DTFR53-09-R-00013.pdf

DTFR53-09-R-00013

SOLICITATION, OFFER AND AWARD

4. TYPE OF SOLICITATION2. CONTRACT NUMBER 3. SOLICITATION NUMBER

7. ISSUED BY CODE 8. ADDRESS OFFER TO (If other than Item 7)

ORDER UNDER DPAS (15 CFR 700)

6. REQUISITION/PURCHASE NUMBER

NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".

NEGOTIATED (RFP)

SEALED BID (IFB)

5. DATE ISSUED

1. THIS CONTRACT IS A RATED RATING PAGE OF PAGES

1 141

C. E-MAIL ADDRESS

EXT.NUMBERAREA CODE

B. TELEPHONE (NO COLLECT CALLS)A. NAME

10. FOR

INFORMATION

CALL:

CAUTION: LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and conditions contained in this solicitation.

(Date)(Hour) local timeuntildepository located in copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if hand carried, in the

SOLICITATION

9. Sealed offers in original and

PART IV - REPRESENTATIONS AND INSTRUCTIONS

OTHER STATEMENTS OF OFFERORS

EVALUATION FACTORS FOR AWARD

INSTRS., CONDS., AND NOTICES TO OFFERORS

REPRESENTATIONS, CERTIFICATIONS AND

LIST OF ATTACHMENTS

CONTRACT CLAUSES

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACH.

I

J

K

L

M SPECIAL CONTRACT REQUIREMENTS

CONTRACT ADMINISTRATION DATA

DELIVERIES OR PERFORMANCE

INSPECTION AND ACCEPTANCE

PACKAGING AND MARKING

DESCRIPTION/SPECS./WORK STATEMENT

SUPPLIES OR SERVICES AND PRICES/COSTS

SOLICITATION/CONTRACT FORM

PART II - CONTRACT CLAUSESPART I - THE SCHEDULE

H

G

F

E

D

C

B

A

SEC. DESCRIPTION PAGE(S) (X) DESCRIPTION SEC. (X)

11. TABLE OF CONTENTS

18. OFFER DATE17. SIGNATURE

SUCH ADDRESS IN SCHEDULE.

IS DIFFERENT FROM ABOVE - ENTER

15C. CHECK IF REMITTANCE ADDRESS

EXT.NUMBERAREA CODE

15B. TELEPHONE NUMBER

(Type or print)AND

ADDRESS

OF

OFFEROR

CODE FACILITY

16. NAME AND TITLE OF PERSON AUTHORIZED TO SIGN OFFER15A. NAME

DATEAMENDMENT NO.DATEAMENDMENT NO.

and related documents numbered and dated):

amendments to the SOLICITATION for offerors

(The offeror acknowledges receipt of

14. ACKNOWLEDGEMENT OF AMENDMENTS

CALENDAR DAYS (%)30 CALENDAR DAYS (%)20 CALENDAR DAYS (%)10 CALENDAR DAYS (%)

(See Section I, Clause No. 52.232.8)

13. DISCOUNT FOR PROMPT PAYMENT

designated point(s), within the time specified in the schedule.

by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the

12. In compliance with the above, the undersigned agrees, if this offer is accepted within ______________ calendar days (60 calendar days unless a different period is inserted

NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

OFFER (Must be fully completed by offeror)

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

28. AWARD DATE

(Signature of Contracting Officer)

27. UNITED STATES OF AMERICA

25. PAYMENT WILL BE MADE BY

26. NAME OF CONTRACTING OFFICER (Type or print)

CODE 24. ADMINISTERED BY (If other than Item 7)

ITEM

(4 copies unless otherwise specified)

23. SUBMIT INVOICES TO ADDRESS SHOWN IN

41 U.S.C. 253 (c) ( 10 U.S.C. 2304 (c) (

22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:

21. ACCOUNTING AND APPROPRIATION20. AMOUNT19. ACCEPTED AS TO ITEMS NUMBERED

AWARD (To be completed by government)

CODE

12/01/2009 X

RAD-30

FRA

Federal Railroad Administration Office of Acq. and Grant Services 1200 New Jersey Avenue SE West Building, 3rd Floor, STOP-50 Washington DC 20590

1630 ES 12/21/2009

Barbara Drook 202 barbara.drook.ctr@dot.gov

493-6460

X

X

X

X

X

X

X

X

X

X

X

X

X

PAGE(S)

Charles Nurse

AUTHORIZED FOR LOCAL REPRODUCTION

Previous edition is unusable

STANDARD FORM 33 (Rev. 9-97)

Prescribed by GSA - FAR (48 CFR) 53.214(c)

1-2 3-16

17-40 41-42 43-44 48-48 49-50 51-64

65-70

71-72

73-78

79-92

93-96

REQUEST FOR PROPOSAL

Railroad Safety Information System (RSIS)

November 18, 2009

This page intentionally left blank i

Contents

PART I

A. SF-33, Solicitation

B. Supplies or Services and Pr ices B.1 Description of Services - General B.2 Base and Option Periods B.3 Schedule of Items and Prices

C. Descr iption/Specifications C.1 Introduction C.2 Statement of Objectives (SOO)

C.2.1 Management Objectives C.2.2 Technical Objectives

C.3 CLIN 001 - RSIS Program, System and Application Management C.4 CLIN 002 - RSIS Data Management Services C.5 CLIN 003 - RSIS Hosting Services C.6 CLIN 004 - RSIS Non-Routine Maintenance, System Development, and

Enhancements C.7 CLIN 005 - Other Direct Costs (ODC’s) C.8 CLIN 006 - Transition of Support Services

D. Packaging and Marking D.1 Packing, Packaging, Marking and Storage of Equipment D.2 Marking D.3 Equipment Removal

E. Inspection and Acceptance E.1 Inspection and Acceptance E.2 Federal Acquisition Regulation (FAR) 52.252-2 Clauses Incorporated By Reference

(JUN 1988)

F. Deliver ies or Per formance F.1 52.252-2 Clauses Incorporated by Reference F.2 Period of Performance F.3 Place of Performance F.4 Reports and Deliverables - CLIN 001 F.5 Task Orders F.6 Task Orders, Placement and Processing F.7 Base Contract and Task Order Administration Costs F.8 Task Order Administration F.9 Contents of Task Orders

G. Contract Administr ation Data G.1 TAR 1252.242-73 Contracting Officer's Technical Representative (Oct. 1994) G.2 Invoice Instructions G.3 Travel and Per Diem G.4 Contract Administration Office ii

H. Special Contract Requirements H.1 Compliance with Regulations H.2 Security Requirements for Unclassified Information Technology Resources

(APR 2005)

H.3 Security

H.3.1 Compliance with Security Regulations, Policies and Procedures H.3.2 Other Pertinent Information or Special Considerations

H.4 Personnel H.4.1 Key Personnel H.4.3 Point Of Contact H.4.4 Contractor Responsibilities/Standards of Conduct

H.5 Training of Contractor/Subcontractor Personnel H.6 Organizational Conflicts Of Interest (OCOI) H.7 Insurance H.8 Provision for Technology Upgrades H.9 Contract Warranty H.10 DOT Trademarks H.11 Release of Proprietary Information H.12 Status of Proposal in Awarded Contract H.13 Requirements Definition H.14 Legal Holidays H.15 Accessibility of Meetings and Conferences to Persons with Disabilities H.16 Contractor Invoicing

I. Contract Clauses I.1 52.252-2 FAR Clauses Incorporated By Reference (FEB 1998) I.2 FAR Clauses I.3 52.216-18 Ordering (OCT 1995) I.4 52.216-19 Order Limitations (OCT 1995) I.5 52.217-8 Option to Extend Services (Nov. 1999) I.6 52.217-9 Option to Extend the Term of the Contract (March 2000) I.7 52.219-17 Section 8(a) Award (DEC 1996) I.8 52.219-18 Notification of Competition Limited to Eligible 8(a) Concerns

(JUN 2003)

I.9 52.232-19 Availability of Funds For The Next Fiscal Year (APR 1984) I.10 52.246-20 Warranty Of Services (MAY 2001)

J . List of Documents, Exhibits and Other Attachments

K. Representations and Cer tifications

L. Instructions, Conditions and Notices to Contractors L.1 Solicitation Provisions Incorporated L.2 Type of Contract L.3 Service of Protest L.4 General L.5 Content of Proposal L.6 Inquiries L.7 Additional Instructions iii

M. Evaluation Factors for Award M.1 Unbalanced Offers M.2 Evaluation Methodology M.3 Evaluation Factors M.4 Price Evaluation M.5 Final Proposal Revision (FPR) M.6 Evaluation Support M.7 Best Value Source Selection Decision M.8 Additional Instructions – Page Limitation

Attachment J-1: RSIS System Overview Attachment J-2: Railroad Accident/Incident Reporting System (RAIRS) Attachment J-3: Railroad Inspection Reporting System (RIRS) Attachment J-4: Grade Crossing Information System (GCIS) Attachment J-5: Government Furnished Equipment Attachment J-6: Past Performance Questionnaire Template Attachment J-7: Sample Quality Assurance Surveillance Plan (QASP ) iv

A. SF-33, Solicitation

PLACEHOLDER FOR SF-33

B. Supplies or Services and Prices

Under the resulting contract, the Contractor will perform services associated with fixed price contract line items and in accordance with task orders for Non-Routine Maintenance, System Development and Enhancements support for the Railroad Safety Information System (RSIS).

The Government may issue task orders against the Not-To-Exceed CLINs listed in Section B.

Loaded labor rates proposed and negotiated prior to contract award will be incorporated into the resulting contract and shall remain fixed for each of the particular contract periods indicated, unless adjustment is necessitated by the appropriate Wage Determination from the Department of Labor, as applicable. The Contractor will be reimbursed for labor expenses by multiplying the negotiated labor rate per discipline by the actual number of labor hours incurred for that discipline during fulfillment of any task orders. Additionally, the Contractor will be reimbursed for material costs based upon the actual cost incurred. Materials as defined herein, consist of all supplies, hardware, and other items not related to the Contractor’s direct labor, which would be necessary for the successful performance of the Security Systems Maintenance. If equipment purchased under task orders causes significant changes in the system size, an adjustment will be negotiated at that time under the changes clause. All Task Orders will be issued by the Contracting Officer after receipt and negotiation of written proposals. Funding for the Task Orders will be obligated at time of issuance. Any purchases of equipment, components or parts must be approved in advance by the Contracting Officer, and will be reimbursed at costs.

Material and handling charges, as applicable, may include all appropriate indirect costs allocated to direct materials in accordance with the Contractor’s usual accounting procedures consistent with FAR Part 31. The contractor shall provide all personnel, facilities, and other incidental materials and services necessary to perform the efforts set forth in Section C – Description / Specifications.

This acquisition is structured as a Performance Based Acquisition in accordance with FAR 37.6.

B.1 Description of Services - General

CLIN Description Vehicle 001 RSIS Program, System, and Application

Management Fixed Price

002 RSIS Data Management Services Fixed Price 003 RSIS Hosting Services Fixed Price 004 RSIS Non-Routine Maintenance, System

Development and Enhancements Indefinite Delivery Indefinite Quantity

005 Other Direct Costs (ODC’s) Reimbursable 006 Transition of Services Fixed Price 007 Optional Award Fee Fixed Price

B.2 Base and Option Periods

The United States Department of Transportation, Federal Railroad Administration intends to make a single award to provide Railroad Safety Information System Services. The base contract will be awarded for a one-year base period, with four (12 month) options to be exercised at the discretion of the Government. The contract will be implemented as a Fixed Price Contract with one Indefinite Delivery-Indefinite Quantity (type) CLIN, and one Reimbursable CLIN.

B.3 Schedule of Items and Prices

BASE PERIOD:

UNIT TOTAL

PRICE PRICE

CLIN SUPPLIES/SERVICES QTY UNIT

001 Program, System, and Application 12 MO _____ ____ _____________ Management Fixed Price

002 Data Management Services 12 MO _____ ____ _____________ Fixed Price

003 Hosting Services 12 MO _____ ____ _____________ Fixed Price

004 Non-Routine Maintenance, System 1 LT MIN $ 10,000.00 Development and Enhancements Indefinite Delivery, Indefinite Quantity NTE $1,000,000.00 [Not to Exceed (NTE) Requirement]

Labor Category Labor Rate

004A Project Manager (PM)

004B Deputy Project Manager (DPM)

004C Lead Developer (LD)

004D Database Administrator/Developer (DBA)

004E SharePoint Administrator (SPA) _____________

004F Operations Manager (OM) _____________

004G Systems/Network Manager (SNM) _____________

004H Systems/Network Engineer (SNE) _____________

004I Software Developer (SD) _____________

004J Oracle/Java Developer (OJD) _____________

004K Sr. Systems Analyst (SSA) _____________

004L Technical Writer (TW) _____________

004M Sr. Data Analyst (SDA) _____________

004N Data /Analyst (DA) _____________

004O Software Quality Assurance/Documentation Specialist (SQA) _____________

005 Other Direct Costs (ODC’s) 1 LT NTE $50,000.00 Reimbursable [Not to Exceed (NTE) Requirement]

006 Turnover/Transition 1 EA _________ _____________ Fixed Price

007 Optional Award Fee 1 EA TBD

OPTION ONE:

UNIT TOTAL

PRICE PRICE

CLIN SUPPLIES/SERVICES QTY UNIT

101 Program, System, and Application 12 MO _____ ____ _____________ Management Fixed Price

102 Data Management Services 12 MO _____ ____ _____________ Fixed Price

103 Hosting Services 12 MO _____ ____ _____________ Fixed Price

104 Non-Routine Maintenance, System 1 LT MIN $ 10,000.00 Development and Enhancements Indefinite Delivery, Indefinite Quantity NTE $1,000,000.00 [Not to Exceed (NTE) Requirement]

Labor Category Labor Rate

104A Project Manager (PM) _____________

104B Deputy Project Manager (DPM) _____________

104C Lead Developer (LD) _____________

104D Database Administrator/Developer (DBA) _____________

104E SharePoint Administrator (SPA) _____________

104F Operations Manager (OM) _____________

104G Systems/Network Manager (SNM) _____________

104H Systems/Network Engineer (SNE) _____________

104I Software Developer (SD) _____________

104J Oracle/Java Developer (OJD) _____________

104K Sr. Systems Analyst (SSA) _____________

104L Technical Writer (TW) _____________

104M Sr. Data Analyst (SDA) _____________

104N Data /Analyst (DA) _____________

104O Software Quality Assurance/Documentation Specialist (SQA) _____________ 105 Other Direct Costs (ODC’s) 1 LT NTE $50,000.00 Reimbursable [Not to Exceed (NTE) Requirement]

106 Turnover/Transition 1 EA _________ _____________

107 Optional Award Fee 1 EA TBD

OPTION TWO:

PRICE PRICE

CLIN SUPPLIES/SERVICES QTY UNIT

201 Program, System, and Application 12 MO _____ ____ _____________ Management Fixed Price

202 Data Management Services 12 MO _____ ____ _____________ Fixed Price

203 Hosting Services 12 MO _____ ____ _____________ Fixed Price

204 Non-Routine Maintenance, System 1 LT MIN $ 10,000.00 Development and Enhancements Indefinite Delivery, Indefinite Quantity NTE $1,000,000.00 [Not to Exceed (NTE) Requirement]

Labor Category Labor Rate

204A Project Manager (PM) _____________

204B Deputy Project Manager (DPM) _____________

204C Lead Developer (LD) _____________

204D Database Administrator/Developer (DBA) _____________

204E SharePoint Administrator (SPA) _____________

204F Operations Manager (OM) _____________

204G Systems/Network Manager (SNM) _____________

204H Systems/Network Engineer (SNE) _____________

204I Software Developer (SD) _____________

204J Oracle/Java Developer (OJD) _____________

204K Sr. Systems Analyst (SSA) _____________

204L Technical Writer (TW) _____________

204M Sr. Data Analyst (SDA) _____________

204N Data /Analyst (DA) _____________

204O Software Quality Assurance/Documentation Specialist (SQA) _____________

205 Other Direct Costs (ODC’s) 1 LT NTE $50,000.00 Reimbursable [Not to Exceed (NTE) Requirement]

206 Turnover/Transition 1 EA _________ _____________

207 Optional Award Fee 1 EA TBD

OPTION THREE:

PRICE PRICE

CLIN SUPPLIES/SERVICES QTY UNIT

301 Program, System, and Application 12 MO _____ ____ _____________ Management Fixed Price

302 Data Management Services 12 MO _____ ____ _____________ Fixed Price

303 Hosting Services 12 MO _____ ____ _____________ Fixed Price

304 Non-Routine Maintenance, System 1 LT MIN $ 10,000.00 Development and Enhancements Indefinite Delivery, Indefinite Quantity NTE $1,000,000.00 [Not to Exceed (NTE) Requirement]

Labor Category Labor Rate

304A Project Manager (PM) _____________

304B Deputy Project Manager (DPM) _____________

304C Lead Developer (LD) _____________

304D Database Administrator/Developer (DBA) _____________

304E SharePoint Administrator (SPA) _____________

304F Operations Manager (OM) _____________

304G Systems/Network Manager (SNM) _____________

304H Systems/Network Engineer (SNE) _____________

304I Software Developer (SD) _____________

304J Oracle/Java Developer (OJD) _____________

304K Sr. Systems Analyst (SSA) _____________

304L Technical Writer (TW) _____________

304M Sr. Data Analyst (SDA) _____________

304N Data /Analyst (DA) _____________

304O Software Quality Assurance/Documentation Specialist (SQA) _____________

305 Other Direct Costs (ODC’s) 1 LT NTE $50,000.00 Reimbursable [Not to Exceed (NTE) Requirement]

306 Turnover/Transition 1 EA _________ _____________

307 Optional Award Fee 1 EA TBD

OPTION FOUR:

PRICE PRICE

CLIN SUPPLIES/SERVICES QTY UNIT

401 Program, System, and Application 12 MO _____ ____ _____________ Management Fixed Price

402 Data Management Services 12 MO _____ ____ _____________ Fixed Price

403 Hosting Services 12 MO _____ ____ _____________ Fixed Price

404 Non-Routine Maintenance, System 1 LT MIN $ 10,000.00 Development and Enhancements Indefinite Delivery, Indefinite Quantity NTE $1,000,000.00 [Not to Exceed (NTE) Requirement]

Labor Category Labor Rate

404A Project Manager (PM) _____________

404B Deputy Project Manager (DPM) _____________

404C Lead Developer (LD) _____________

404D Database Administrator/Developer (DBA) _____________

404E SharePoint Administrator (SPA) _____________

404F Operations Manager (OM) _____________

404G Systems/Network Manager (SNM) _____________

404H Systems/Network Engineer (SNE) _____________

404I Software Developer (SD) _____________

404J Oracle/Java Developer (OJD) _____________

404K Sr. Systems Analyst (SSA) _____________

404L Technical Writer (TW) _____________

404M Sr. Data Analyst (SDA) _____________

404N Data /Analyst (DA) _____________

404O Software Quality Assurance/Documentation Specialist (SQA) _____________

405 Other Direct Costs (ODC’s) 1 LT NTE $50,000.00 Reimbursable [Not to Exceed (NTE) Requirement]

406 Turnover/Transition 1 EA _________ _____________

407 Optional Award Fee 1 EA TBD

Labor Categories

The following Labor Categories (and others specified by the contractor) and associated descriptions are illustrative of the type of support anticipated for RSIS.

Key personnel are denoted with *.

Project Manager (PM)* - Project Management professional responsible for oversight of RSIS development, data management and IT infrastructure and services operations. The PM is responsible for developing project plans on the RSIS program. The PM manages each project phase to ensure that it is completed on time and within budget. The PM interfaces with project team members, vendors, executive staff, FRA principals and provides status reports to the COTR. The PM ensures alignment and compliance with FRA/DOT/OMB IT governance policies including Enterprise Architecture, Capital Planning and Investment Control (including Earned Value Management reporting), IT Security and Records Management.

Note: The Government anticipates that this will be a half-time position (1/2 FTE).

Deputy Project Manager (DPM) *- Experienced Capability Maturity Model Integration (CCMI) trained professional responsible for managing the RSIS software development lifecycle (SDLC). The DPM assists the PM in developing project plans for system development and modernization tasks and process improvement initiatives. The DPM serves as the project’s requirements manager and develops test plans for new systems and enhancements to existing applications. The DPM oversees the contractor’s change control process.

Lead Developer (LD) *– Senior Software Development professional responsible for overseeing activities of application developers who support client, network (client-server) and web applications. Environment includes .NET, SAS Business Intelligence (BI), MS SharePoint 2007 (MOSS), MS Visual Studio.NET, web services and a host of third party development tools (Adobe Flex, MS Silverlight, dashboards, charting, OLAP viewers, ETL tools). The LD will also be responsible for evaluating and recommending current technologies to improve the manner in which RSIS collects, maintains and disseminates information to its stakeholders.

Database Administrator/Developer (DBA) – Senior database professional responsible for providing technical expertise in the design, implementation, and maintenance of core relational database management systems that support the RSIS enterprise applications. The DBA will manage the RSIS production databases (MS SQL Server, SAS, OLAP cubes and other data aggregations), client application databases (MS Access, MySQL), and SharePoint content databases. The DBA will also oversee the various Extract, Transform and Load (ETL) processes for RSIS.

SharePoint Administrator (SPA) – Senior SharePoint Administrator professional responsible for designing, configuring and maintaining internal and external SharePoint farms and content databases to support RSIS requirements. The SPA interacts with the PM/DPM to help define requirements and create solutions based on SharePoint. In addition, the SPA will work with the RSIS project technical leads to apply industry accepted best practices and the principles and processes uniquely related to SharePoint in developing efficient and effective application solutions. The SPA is responsible for user account administration and authentication.

Operations Manager (OM) – Senior data management professional responsible for overseeing production data processing lifecycle including receipts control, data entry, data editing and validation, deficiency prevention, data quality assurance and data delivery. The OM supervises a staff of data analysts who receive, input, cleanse and validate RSIS data prior to publication on the FRA website and other outlets.

Systems/Network Manager (SNM)* – Senior network professional responsible for overseeing day-to-day RSIS Production and Disaster Recovery (DR) infrastructure operations, capacity planning, resource management, and documentation of processes to deploy and maintain applications. Also responsible for

Sr. Systems Analyst (SSA)*– Senior analyst serving as subject matter expert on FRA regulations under Section 49 of the Code of Federal Regulations (CFR). The SSA interfaces with FRA Office of Safety principals to document business requirements arising from regulatory changes and translates those into technical specifications (database and application) for RSIS sub-systems. The SSA participates in FRA regulatory working group discussions to assess and advise on data management requirements. The SSA works with the software development team during the design and test phases of the SDLC.

implementing, maintaining and troubleshooting communications circuits, servers, storage area networks, desktops, and networking equipment.

Specific technologies and applications include Active Directory, SQL Server, Oracle, IIS, Linux, VMWare, SharePoint, MS-Exchange ESRI GIS, and Cisco network security software and appliances. The SNM serves as the project’s Information System Security Officer (ISSO). The SNM provides technical expertise in a variety of server and networking technologies including server consolidation and virtualization. The SNM is responsible for keeping infrastructure diagrams current and is the principal technical representative to the FRA Change Control Board

(CCB).

Systems/Network Engineer (SNE) – Network professional responsible for the support and maintenance of the RSIS production and DR network infrastructure. The SNE administers RSIS and hosted servers and works under the direction of the SNM in planning and executing infrastructure projects. The SNE ensures that OS versions and patch levels are compliant with FRA/DOT standards and that Security Plan of Action and Milestones (POAMs) and vulnerabilities are remediated within the prescribed window. The SNE provides technical support with VLANs, VPNs, IT Security, data replication and data encryption. The SNE assists in maintaining the current RSIS Government Furnished Equipment (GFE) list as well as the FRA standard image.

Software Developer (SD) – Experienced application developer responsible for the development, enhancement and maintenance of RSIS client and web-based applications. The SD leverages a strong understanding of Microsoft .NET development environments and UML methodologies in delivering software work products. Development environment includes, but is not limited to MS .NET, Visual Studio .NET, C#, JavaScript, SASBI, SQL Server, SharePoint BDC, Web parts, Web Services and a host of third-party products, Oracle/Java Developer (OJD) – Part-time Oracle /Java developer to support the FRA Office of Chief Counsel’s (RCC’s) Railroad Enforcement System (RES) and its RSIS interfaces.

Environment consists of Red Hat Linux 7, Oracle 11g/10g Developer Suite, Java/JSP, Struts, AJAX and PL/SQL.

Technical Writer (TW) – Experienced writer responsible for assisting in the development of FRA instruction manuals and reporting guides in support of the agency’s Accident/Incident, Highway-Rail Crossing and Rail Safety Improvement Act (RSIA) reporting mandates. The TW has a strong working knowledge of FRA regulatory requirements under Section 49 of the Code of Federal Regulations and interfaces with FRA subject matter experts on matters of content and format for the required publications. The TW serves as content resource for the application development team on RSIS work products.

Sr. Data Analyst (SDA) – Experienced data professional with strong command of FRA Accident/Incident (A/I) reporting rules under 49 CFR 225. The SDA will regularly interface with FRA A/I experts to resolve issues of compliance and reportability. The SDA communicates with railroad safety reporting officers to resolve reporting errors and deficiencies.

Data Analyst (DA) – Responsible for the entry, editing and validation of railroad safety reports submitted to FRA in hard copy or electronic format.

Software Quality Assurance/Documentation Specialist (SQA) – Responsible for executing test plans and documenting results of RSIS client and web application products. Prepares end-user documentation and release notes for RSIS applications. The SQA routinely updates reference tables utilized by RSIS applications. The SQA assists in the design and development of FRA forms and instructions for OMB approval.

C. Description/Specifications

C.1 Introduction

The Railroad Safety Information System (RSIS) (See attachment J-1 for system overviews) is the FRA’s principal repository for data related to railroad accidents and incidents, inspections, highway-rail crossings and other rail safety related information. RSIS is used extensively by FRA to monitor and report on the current state of safety in the railroad industry. The information in RSIS is made available to a variety of stakeholders including railroads, rail labor, other Federal, State and local agencies, non-governmental organizations, academia and the general public primarily through FRA’s Safety data websites.

RSIS is used by FRA for the following:

• Providing a central and authoritative source for rail safety information;

• Safety trend and risk analysis;

• Accident/Incident Reporting compliance (Situational awareness/incident reporting of rail incidents and employee fatalities);

• Data/statistical/economic analysis for rulemaking support and regulatory evaluation;

• Supporting compliance monitoring and enforcement efforts;

• Performance/Budget reporting under the Government Performance Results Act (GPRA);

• Resource allocation through FRA’s National Inspection Plan (NIP);

• Promoting highway-rail crossing safety and trespass prevention education, outreach and communication efforts;

• e-Gov and data sharing services for the rail industry and other Federal agencies;

• Inspector performance management.

The Office of Safety supports FRA in collecting, validating and managing safety related matters with respect to the railroad industry through RSIS. The FRA regulations on reporting railroad accidents/incidents are found primarily in Title 49 of the Code of Federal Regulations (CFR), Part 225 (49 CFR Part 225). The purpose of the regulations in Part 225 is to provide FRA with accurate information concerning the hazards and risks that exist on the nation’s railroads. FRA needs this information to effectively carry out its regulatory and enforcement responsibilities under the Federal railroad safety statutes. Issuance of these regulations preempts States from prescribing accident/incident reporting requirements. FRA also uses this information for determining comparative trends of railroad safety and to develop hazard elimination and risk reduction programs that focus on preventing railroad injuries and accidents.

RSIS is comprised of the following principal systems:

1. Railroad Accident Incident Reporting System (RAIRS) – RAIRS

(See attachment J-2 for system overviews.)

This system compiles accident/incident data that railroads are required to submit under 49 CFR Part 225. Approximately 35 years of data on railroad injuries and illnesses, train accidents, highway-rail crossing collisions and operational statistics are contained in this system. In addition to collecting and archiving railroad accidents/incidents data, some of the other specific objectives of the (RAIRS) component of RSIS are:

a. Provide means to effectively and accurately collect, assess, manage, and report on accident/incident data statistics including train accidents, injuries and highway-rail crossing collisions;

b. Contribute to the agency’s mission of promoting railroad safety to 1) reduce the train accident rate (accidents per million train miles); 2) reduce the grade crossing accident rate; 3) reduce the rail related fatality rate; 4) reduce the rail related injuries rate; 5) reduce the number of HAZMAT releases;

c. Provide timely distribution and availability of railroad accident/incident data;

d. Provide government agencies, railroad labor and management, and the general public with authoritative information on railroad safety;

e. Provide the means to assess the state of railroad safety in the industry;

f. Provide trend data and safety statistics to support the agency’s regulatory and enforcement mission;

g. Support ongoing initiatives within the agency in the areas of risk management, fatigue avoidance, crew management and others.

2. Railroad Inspection Reporting System (RIRS) – RIRS

(See attachment J-3 for system overviews.)

This system is the record repository of all FRA and State railroad inspections, defects and violations. RIRS compiles enforcement and compliance data that is essential for FRA to achieve its strategic goal of safety and organizational excellence. The RIRS subsystem supports the following related objectives:

a. Provide means to effectively and accurately collect, assess, manage, and report on safety violations and inspection/compliance data statistics collected by FRA;

b. Provide resources and tools for federal and state safety inspectors to manage workload and resources, to better manage inspection time and to ensure that high-risk areas are in compliance with Federal law and regulations;

c. Perform resource allocation of inspectors, to determine safety performance of railroads, to determine ways to reduce highway user and train collisions, and to reduce trespasser/pedestrian injuries and fatalities;

d. Provide the National Inspection Plan (NIP) allocation programs to use predictive indicators for distributing inspection activities within a region by railroad and by state to reduce train accidents;

e. Provide timely distribution of railroad inspection data;

f. Provide the ability to record enforcement actions on regulatory violations that are leading causes of train accidents;

g. Provide means to determine systemic problems that affect a railroad over many states and regions thus revealing many defective conditions e.g. deferred maintenance, improper repair orders, etc.;

h. Support on-line trend analysis, and the tracking of industry defect remediation actions;

i. Measure inspector performance and effectiveness.

3. Highway-Rail Grade Crossing Inventory System (GCIS) – GCIS

(See attachment J-4 for system overviews.)

This is the principal database that contains the attributes of the nation’s highway-rail crossing intersections. GCIS is used extensively by FRA, State Highway agencies and railroads as the authoritative source of information for planning safety improvements to crossings and to prevent collisions and casualties. Some of the specific objectives of GCIS are:

a. Provide physical attributes and exposure (frequency of automobile traffic and number of trains per day) for the highway-rail intersections (crossings) for use with DOT’s Accident Prediction Model;

b. Support a valid statistical method of determining which highway railroad crossings are eligible to receive funding to improve warning systems;

c. Support the agency’s outreach efforts to educate the general public on the hazards at highway-rail crossings;

d. Serve as the definitive source for identifying the nation’s most hazardous crossings and plan strategies to improve safety at those locations;

e. Record and disseminate information on highway-rail grade crossing safety data to states and railroads for local crossing investigations and railroad safety duties;

f. Provide historical data on maintenance of the highway rail crossing site inventory;

g. Support FRA enforcement of regulations such as the Train Horn Rule.

NOTE: The passing of the Rail Safety Improvement Act of 2008 (RSIA) changes the GCIS landscape altogether in that it now mandates the updating and maintenance of inventory information. Under Section 204, RSIA requires that railroads and States report on the characteristics of highway-rail crossings at grade, including dedicated pathways (pedestrian) crossings, to DOT National Crossing Inventory.

4. Expanding Electronic Government (e-Gov) - RSIS

Supports the President’s Management Agenda in Strategic Area #4: “Expanding Electronic Government” by collecting and providing safety data via the internet through its public and private secure websites, thus promoting Government-to-Government, Government-to- Business, and Government-to-Citizen on-line communications on various safety related issues. The RSIS website (http://safetydata.fra.dot.gov/) is a one-stop site that:

a. Provides a national-level source for railroad safety data that is secure and authoritative;

b. Provides access to visitors of the website to safety information including accidents/incident, inspections, and highway-rail crossing data;

c. Provides the capability to run dynamic queries, and download safety database files and forms, manuals, latest rulings on reportability of accidents and injuries, and view current statistical information on railroad safety;

d. Provides railroads with a special secure website to allow downloading of FRA inspection and violation data for railroads to track and remediate deficiencies;

e. Communicates completion of inspection reports to railroads via e-mail;

f. Provides highway-rail crossing data to citizens, including maps, accidents, predictions, as well as federal, state, railroad, and organization contacts.

C.2 Statement of Objectives (SOO)

The overarching objective of this effort is to provide and maintain an authoritative Railroad Safety Information System.

The management objectives are: (a) allow the contractor maximum flexibility to innovatively manage program cost, schedule, performance, risks, warranties, contracts and sub-contracts, vendors, and data required to deliver an effective and affordable system and (b) maintain clear government visibility into program cost, schedule, technical performance and risk.

The technical objectives of FRA’s RSIS are to: (a) collect and disseminate railroad accident and incident information; (b) support inspection of railroads; (c) manage the highway - rail crossing inventory; (d) share information with Communities of Interest (COIs) and; (e) comply with standard federal regulations (FISMA, OMB’s Federal Enterprise Architecture).

The objectives are expanded in sections C.2.1 and C.2.2 and include some of the performance measures that will be required.

C.2.1 Management Objectives

Project Management Objectives The project management objectives are to (i) provide support for overseeing resource management activities to include budgeting, programming and accounting; (ii) provide support for development, preparation, submission, and justification of budget exhibits and request for information for FRA’s A-11 Capital Planning and Investment Control (CPIC) requirements.

Project Visibility Objectives The objectives are to (i) provide clear and concise work breakdown structures; (ii) provide regularly updated project plan measured against the baseline; (iii) utilize earned value management reports to identify potential schedule risks and cost overruns; and (iv) provide status reports with issues, risks and mitigation strategies.

Management Oversight and Reporting

Timeliness: The % of required reports that are made available to the government by the scheduled due date.

Expectation: Meets: 100% of reports on time

Unsat: < 100% of reports on time

C.2.2 Technical Objectives Railroad Accident/Incident Objectives The objectives are to (i) collect, assess, manage, and report on accident/incident data statistics including injuries, highway-rail crossing collisions; (ii) contribute to a reduction in the number of train accidents and incidents per million train miles; (iii) provide timely distribution of railroad accident/incident data to FRA management, government agencies, railroad labor and management, and the general public.

Manage and Maintain Railroad Accident/Incident Reporting System (RAIRS)

Availability: The number of days elapsed to edit, validate and analyze the accident/incident reports submitted by the railroads and made available to FRA with acceptable quality.

Expectation: Exceeds: < 25 days Meets: ≤ 31 days Unsat: > 31 days

Correctness: The % of the records that have gone through extensive cross-validation and have been accepted to be correct and valid when released to FRA.

Expectation: Meets: = 100% Unsat: < 100%

Completeness: The % of railroads by regulation that have to submit a report that have submitted one.

Expectation: Exceeds: ≥ 95% Meets: ≥ 90% Unsat: < 90%

Railroad Inspection Objectives The objectives are to (i) collect, assess, manage, and report on safety violation and inspection data statistics; (ii) provide the resources to National Inspection Plan (NIP) allocation programs to use predictive indicators to manage workload and to better manage inspection time and to ensure that high-risk areas are in compliance with Federal law and regulations; (iii) provide timely distribution of railroad inspection data; (iv) record enforcement actions on regulatory violations that are leading causes of accidents; (v) determine systemic problems and defective conditions;

(vi) track and report on industry defect remediation actions.

Manage and maintain Railroad Inspection Reporting System (RIRS)

Completeness: The % of inspection reports that have been updated are processed to the FRA RIRS database.

Expectation: Exceeds: ≥ 99% Meets: ≥ 95% Unsat: < 95%

Grade Crossing Objectives The objectives are to (i) collect, assess, manage, and report on highway-rail inventory data; (ii) support a valid statistical method of determining which highway railroad crossings are eligible to receive funds to improve warning systems; (iii) record and disseminate information on highway-rail grade crossing data to public, state and railroads to promote safety.

Manage and Maintain Grade Crossing Inventory System (GCIS)

Correctness: The % of the records that have gone through extensive cross-validation and have been accepted to be correct and valid when released to FRA.

Expectation: Meets: = 100% Unsat: < 100%

Information Sharing Objectives The Communities of Interests (COIs) are (a) Department of Transportation, (b) railroad and related industries, (c) other federal agencies, (d) state and local government and (e) citizens.

The objectives are to (i) provide railroads with a special secure web site to allow downloading of FRA inspection and violation data for railroads to track and remediate deficiencies; (ii) provide a public website for railroad safety data including accidents and incidents, and highway-rail crossing data; (iii) provide the capability to run dynamic queries, download railroad safety data, and view current statistical information on railroad safety; (iv) provide a secure private site with visibility determined by established security levels, for FRA and its state partners to review accident, casualty, inspection, and other data to assist management and other decision makers in taking the right actions to promote safety within the railroad industry.

System Support

Availability: The % of time the system (website and database) is up and available to the end user during 24/7 operations.

Expectation: Exceeds: > 99.9% availability Meets: ≥ 99.3% availability Unsat: < 99.3% availability

Compliance Objectives The objectives are to (i) achieve and maintain compliance with IT Governance Policies as required under Federal, DOT and FRA regulations and policies, as updated, including but not limited to OMB Circular A-130; the Federal Information Security Management Act (FISMA) of 2000, and as identified in the National Institute of Standards and Technology (NIST) Guidelines, and (ii) align and support the FRA Enterprise Architecture (EA) policies consistent with the Federal Enterprise Architecture reference models.

C.3 CLIN 001 - RSIS Program, System and Application Management

General Requirements:

The contractor shall be responsible for managing the day-to-day business activities, system development and maintenance, infrastructure management and technical and administrative support necessary to ensure successful completion of the contract objectives, and efficient functioning of the RSIS operations. These requirements include:

• Program Management and IT Governance Support

• RSIS Infrastructure Management

• RSIS Application Management, encompassing:

o Production Data Management o RSIS Client applications o RSIS Web presences and application systems o RSIS SharePoint systems

• State Inspector IT Support

• Help Desk Operations

• Other Support Requirements

Note to Contractor: On a case-by-case basis; services obtained under CLIN 004 (RSIS Non- Routine Maintenance, System Development, and Enhancements) “may” transition to CLIN 001 for sustainment. This will occur only once yearly, when option years are negotiated and subsequently exercised.

1.1 Project Management and IT Governance Support

The contractor shall submit an initial detailed project plan not later than ten (10) business days after contract award. The project plan shall clearly outline the steps to be performed to complete all the tasks under this contract, and ensure on-time delivery to the government of all commitments. At a minimum, the contractor’s project plan shall provide proposed start and end dates that conform to the contract deliverables and a work breakdown structure for all tasks to be accomplished in RSIS. The contractor shall refine the details of the initial project plan (based on knowledge acquired from meetings and discussions with the COTR and staff, as well as actual work performed), and submit a Final Project Plan within 45 days of contract award. The Final Project Plan shall identify recurring detailed deliverables such as logs, reports and electronic data files.

The Contractor shall provide monthly status briefs and reports for the duration of this contract.

Specific format and content of these reports shall be determined at the initial kickoff meeting. At a minimum, status reports will compare actual progress against baseline project plans as follows:

• Provide monthly briefs, factual summary description of technical progress made and hours incurred for each task (or groups of tasks) during the reporting period;

• Identify issues and/or risks that impact technical performance or schedule;

• Provide monthly updates to project plan, including the degree of completion of tasks/activities by time intervals compared against the approved project plan baseline;

• Describe planned activities for the next reporting period.

The contractor shall schedule and conduct an In-Process Review (IPR) meeting with the COTR at the mid-point of each quarter (no later than the 60th

1.2 RSIS Infrastructure Management

day of each performance quarter). The purpose of the IPR is to discuss the progress of the tasks relative to cost and schedule as well as identify outstanding issues and risks. The IPR will be used by the government to ensure that the program is on-schedule, within budget and any outstanding issues are addressed.

The contractor shall schedule and conduct a quarterly Contractor Performance Review meeting with the COTR at the end of each contract quarter. The contractor shall submit its Quarterly Self-Assessment Report (QSAR) which will, based on the COTR’s assessment and the agreed upon Quality Assurance and Surveillance Plan (QASP), be the basis for performance awards as determined by the fee plan for this contract.

The current RSIS production facility houses a server room with racks that contain the Government Furnished Equipment (GFE) detailed in attachment J5. This equipment includes servers, network and security appliances. The RSIS Disaster Recovery (DR) presence is maintained at a data center facility approximately 90 miles away in Richmond, VA. Automated data replication is conducted between the production and DR facilities to allow for a ‘warm’ failover when problems occur at the production facility.

The contractor shall be responsible for operating and maintaining the RSIS systems and infrastructure consistent with FRA and DOT policy including but not limited to:

• Server Management

• Network Administration

• Configuration Management

• Security/Patch Management

• GFE Maintenance/Management

• Disaster Recovery

The contractor shall provide a representative to the weekly FRA Change Control Board (CCB) meetings to act as the RSIS technical resource. The RSIS technical resource shall report all planned system modification and changes using the prescribed system change request form. The contractor shall ensure that any and all configuration changes to RSIS go through the FRA CCB process. The contractor shall be responsible for status reporting and system documentation for CCB approved changes including updates to the system security plan to reflect CCB-approved changes to RSIS.

1.3 RSIS Application Management

This section describes the requirements for managing the suite of RSIS client, web, SharePoint and specialized applications.

Production Data Management Applications

The contractor shall be responsible for maintaining the suite of RSIS data management programs used for the input, editing and validation of RSIS data prior to release and publication. These data management applications include:

• RAIRS and GCIS production data entry/capture programs;

• Railroad Reflectorization Rule data entry;

• Continuous Welded Rail (CWR);

• Automated RISPC data processing routines;

• AIRGNET and GX32 data processing routines;

• Batch Edit and Validation programs;

• Extract, Transform and Load (ETL) routines for all data deliveries;

• Web services for RAIRS, RIRS, GCIS and related RSIS systems;

• Reference table maintenance programs and services;

• Securesite access and permissions management programs.

Client Applications

The contractor shall be responsible for managing the maintenance, distribution and support of the FRA-provided client applications. These applications include:

• Railroad Inspection Program for the PC (RISPC) – This .NET application program is provided to FRA and State inspectors for their use in recording, printing and uploading their railroad safety inspections.

• Accident/Incident Report Generator (AIRGNET) – This .NET program is provided to railroad carriers for their use in complying with the accident/incident reporting requirements under 49 CFR 225.

• Highway-Rail Crossing Data Management Program (GX32). - This legacy Visual Basic application is provided to State Highway organizations and railroads to manage, maintain and update the attributes of the highway-rail crossings within their jurisdictions.

Each GX system comes with a custom database suited to the requestor’s inventory of crossings.

• PC Accident Prediction System (PCAPS) – This legacy Visual Basic program is provided to FRA staff, State agencies, railroads and other organizations to produce priority lists (in predicted accident order) of the crossings in their jurisdictions. It is used as a basis for obtaining funding for crossing improvement projects under the Federal Highway Administration’s (FHWA’s) Section 130 program.

The contractor shall be responsible for managing the distribution and maintenance of the RSIS client applications.

RSIS Web Applications

The contractor shall be responsible for routine update and maintenance of the RSIS web applications. The current suite of RSIS web applications falls under the following general categories:

• Safetydata public web site (http://safetydata.fra.dot.gov) – The public site has long been the authoritative repository for FRA railroad safety statistics, forms and publications.

The site was built using ASP.NET, C# and third party products. All of the query interfaces are customizable utilizing multiple drop-down menus to produce reports when run against the SASBI (Business Intelligence) platform and SQL Server back end data sources. In addition to a host of user-customizable queries, the public site has a “Data on Demand” utility from which users can obtain the accident/incident and grade crossing inventory records in a variety of formats. Metadata and other reference tables are also available. A web based Geographic Information System (GIS) that is based on the ESRI platform is also available for generating maps and other geospatial reports. An application called the Web-Based Accident Prediction System (WBAPS) is hosted on the public site and used for generating reports ranking highway-rail crossings by their predicted accident values.

• Safetydata secure web site – The securesite, as it is referred to, is accessible to FRA employees (primarily in the Office of Safety) and State inspectors/managers and contains information on FRA…