FRA_RSIMSS_Solicitation_DTFR53-15-R-00115_-_4_Sep_15.pdf
PDF 3 MB Posted
- Solicitation number
- DTFR5315R00115
About this file
FRA RSIMSS Solicitation DTFR5315R00115
View the file
Other files
Show all 12
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
DTFR5315R00115
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 148
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
09/04/2015 X
FRA RAD-30
Federal Railroad Administration Office of Acquisition Services 1200 New Jersey Avenue SE West Building, 3rd Floor, Stop-50 Washington DC 20590
1200 ES 10/05/2015
Corey Scott 202 corey.scott@dot.gov
493-6150
X
X
X
X
X
X
X
X
X
X
X
X
X
PAGE(S)
Corey Scott
AUTHORIZED FOR LOCAL REPRODUCTION
Previous edition is unusable
STANDARD FORM 33 (Rev. 9-97)
Prescribed by GSA - FAR (48 CFR) 53.214(c)
2-8
9-24 27-28 29-30 31-55
56-69
70-110
111-138
139-145
146-148
SECTION B – SUPPLIES OR SERVICES AND PRICES AND COSTS
B.2 SCHEDULE OF PRICING
Base Period of Performance: January 1, 2016 through December 31, 2016 IDIQ Contract CLIN Structure
CLIN Description of Services
QTY
(FFP)
UNIT
(FFP)
TOTAL
PRICE
(FFP)
QTY or
ESTIMATED
HOURS
(LH)
FULLY
LOADED
HOURLY
LABOR
RATES
(Cumulative)
(LH)
NTE
ESTIMATED
PRICE
(LH)
00001 Program, Systems, Data and Application Management (O&M)
NA NA NA
00002 Non-Routine Maintenance, System Development and Enhancements
00003 Transition In
00004 Transition Out NA NA NA
Contract Line Item Numbers (CLINs) 00001, 00003 and 00004 shall be Firm-Fixed Price (FFP)
CLINs. The majority of Task Orders (TOs) issued against CLIN 00002 will be FFP, with the capability for Labor Hour (LH) TOs issued against CLIN 00002, if required.
The following are labor categories based on historical usage, although the contractor may suggest their own mix of labor categories:
Project Manager*
Deputy Project Manager*
Task Lead
Senior Data Analyst
Senior Solution Manager
Data Analyst
Technical Writer
Documentation Specialist
*Indicates Key Personnel.
PRICING SCHEDULE FOR BASE PERIOD
Labor Category Fully Loaded Rate
Option Year One Period of Performance: January 1, 2017 through December 31, 2017 IDIQ Contract CLIN Structure
QTY
(FFP)
UNIT
(FFP)
TOTAL
PRICE
(FFP)
QTY or
ESTIMATED
HOURS
(LH)
FULLY
LOADED
HOURLY
LABOR
RATES
(Cumulative)
(LH)
NTE
ESTIMATED
PRICE
(LH)
10001 Program, Systems, Data and Application
10002 Non-Routine Maintenance, System Development
10003 Transition In
10004 Transition Out NA NA NA
CLINs 10001, 10003 and 10004 shall be FFP CLINs. The majority of TOs issued against CLIN
10002 will be FFP TOs with the capability for LH TOs issued against CLIN 10002, if required.
PRICING SCHEDULE FOR OPTION YEAR ONE PERIOD
Labor Category Fully Loaded Rate
Option Year Two Period of Performance: January 1, 2018 through December 31, 2018 Task Order Structure
QTY
(FFP)
UNIT
(FFP)
TOTAL
PRICE
(FFP)
QTY or
ESTIMATED
HOURS
(LH)
FULLY
LOADED
HOURLY
LABOR
RATES
(Cumulative)
(LH)
NTE
ESTIMATED
PRICE
(LH)
20001 Program, Systems, Data and Application
20002 Non-Routine Maintenance, System Development
20003 Transition In
20004 Transition Out NA NA NA
CLINs 20001, 20003 and 20004 shall be FFP CLINs. The majority of TOs issued against CLIN
20002 will be FFP TOs with the capability for LH TOs issued against CLIN 20002, if required.
PRICING SCHEDULE FOR OPTION YEAR TWO
Labor Category Fully Loaded Rate
Option Year Three Period of Performance: January 1, 2019 through December 31, 2019 IDIQ CLIN Structure
QTY
(FFP)
UNIT
(FFP)
TOTAL
PRICE
(FFP)
QTY or
ESTIMATED
HOURS
(LH)
FULLY
LOADED
HOURLY
LABOR
RATES
(Cumulative)
(LH)
NTE
ESTIMATED
PRICE
(LH)
30001 Program, Systems, Data and Application
30002 Non-Routine Maintenance, System Development
30003 Transition In
30004 Transition Out NA NA NA
CLINs 30001, 30003 and 30004 shall be FFP CLINs. The majority of TOs issued against CLIN
30002 will be FFP TOs with the capability for LH TOs issued against CLIN 30002, if required.
PRICING SCHEDULE FOR OPTION YEAR THREE
Labor Category Fully Loaded Rate
Option Year Four Period of Performance: January 1, 2020 through December 31, 2020 IDIQ CLIN Structure
QTY
(FFP)
UNIT
(FFP)
TOTAL
PRICE
(FFP)
QTY or
ESTIMATED
HOURS
(LH)
FULLY
LOADED
HOURLY
LABOR
RATES
(Cumulative)
(LH)
NTE
ESTIMATED
PRICE
(LH)
40001 Program, Systems, Data and Application
40002 Non-Routine Maintenance, System Development
40003 Transition In
40004 Transition Out NA NA NA
CLINs 40001, 40003 and 40004 shall be FFP CLINs. The majority of TOs issued against CLIN
40002 will be FFP TOs with the capability for LH TOs issued against CLIN 40002, if required.
PRICING SCHEDULE FOR OPTION YEAR FOUR
Labor Category Fully Loaded Rate
B.2.1 Additional Pricing Guidance for Applicable to All Schedule of Pricing (Base and Option Period of Performance)
Firm Fixed Price Total and Labor Hour Prices shall be inclusive of total allowable costs, i.e., fully loaded hourly rates. Fully loaded hourly rates include elements such as salary, fringe benefits, overhead, G&A, etc. G&A is allowable against any material costs proposed for LH type task orders.
B.3 MINIMUM GUARANTEE
B.3.1 The minimum guarantee value for this requirement is $25,000.00 over the life of the contract.
END SECTION B
SECTION C – DESCRIPTION/SPECIFICATIONS/STATEMENT OF OBJECTIVES
C.1 Definition – Statement of Objectives
Per Federal Acquisition Regulations, Subpart 2.1, Definitions - Statement of Objectives (SOO) means a Government-prepared document incorporated into the solicitation that states the overall performance objectives. It is used in solicitations when the Government intends to provide the maximum flexibility to each offeror to propose an innovative approach.
C.2. Background Information
C.2.1 The United States Department of Transportation (DOT) Federal Railroad Administration
(FRA) Office of Railroad Safety (RRS) has a need for data and knowledge management support services, hereinafter referred to as Railroad Safety Information Management Support Services
(RSIMSS) that will enable sound data management practices and consistently high quality delivery of railroad safety and safety-related data, hereafter aggregately railroad safety data, and information assets to FRA and its stakeholders.
FRA maintains railroad safety data dating back to 1975 and the reporting, data management, and data analysis processes have evolved over time into an overarching safety data program known as the Railroad Safety Information System (RSIS). The majority of safety data collected and managed via the RSIS program is regulation data. This data is mandated to be collected and maintained by RRS (specifically, FRA Chief Safety Officer) and has the specifics regarding format and submission method detailed through the rulemaking process. The Railroad Safety information Management Division (RSIMD) has the mission of planning and directing all activities relating to the management of the Office of Safety’s information assets and use of the data, ensuring availability and accuracy of the railroad safety knowledge resources, and serving as the authoritative source.
To achieve the vision of maintaining a single authoritative data source for railroad safety data, RSIMD has undertaken a number of projects focusing on its principal safety data system, RSIS, and its underlying data structure. RSIS is comprised of a series of subsystems for housing and processing various data types with some integration across datasets. The principal subsystems include:
Railroad Accident/Incident Reporting System (RAIRS) comprising railroad accident/incident data, highway-rail collision data, operational data, and injury and illness data required under 49 CFR Part 225
Railroad Inspection Reporting System (RIRS) comprising compliance and enforcement data including defects and proposed violations collected through FRA and State inspections
Highway-Rail Grade Crossing Inventory System (GCIS) comprising inventory, equipment, and characteristic information about highway-rail crossing intersections.
In addition to the principal subsystems, RSIS also maintains safety data portals (public and secure/private) to disseminate and distribute railroad safety data, reports, and information to its stakeholders, an investigation reporting system for collecting accident investigation reports, a
SharePoint portal for collecting data and information not falling into the three primary datasets
(such as required railroad plan submissions with routing and approval workflow), and various other data management solutions such as the Activation Failure / False Proceed (AF/FP) report for recording AF/FP investigations. More details about RSIS and a complete list of applications and systems contained within can be found in Attachment 2.
Historically, RSIMD was primarily focused on getting the data on time into RSIS; however, RSIMSS will enable RSIMD to perform the requisite planning, analysis, and enhancement with an emphasis on streamlining the data collection processes from a business perspective. The optimization of processes and integration of datasets will shift the paradigm of the safety data collection program and will require modern, flexible solutions that can be accessed from a variety of methods across data stakeholder groups. A goal of these efforts will be to generate efficiencies in all aspects of the data management process including operations, maintenance, and enhancement and position RSIS to be a platform that enables the uploading, analysis, and distribution of FRA safety data and information to FRA’s stakeholders.
C.3 Envisioned Scope
C.3.1 The primary scope and objective of the resulting RSIMSS contract will provide safety data management support services that will enable FRA to accomplish mission objectives. This SOO is designed to provide Contractors with a framework of efficient and highly effective services to fulfill the safety data management needs from the data collection process through safety data strategy development and implementation and subsequent safety data management tool maintenance for the next five years. The scope of work will often require the Contractor to coordinate, and at times collaborate, with the FRA Office of Information Technology to accomplish the goals and objectives of RSIMSS. The main focus will be around establishing an efficient data management solution and schema to enable the publishing of data and the framework for a data exchange between FRA and its stakeholders, while striving for continuous improvement.
C.3.2 FRA will use an Indefinite Delivery, Indefinite Quantity (IDIQ) contract vehicle for the
RSIMSS contract and include the following support service areas to support the overall contract objectives:
a. Safety Data Management Support Services
b. Safety Data Collection Support Services
c. Safety Data Management Program Planning Support Services
d. Safety Data Distribution and Data Analysis Support Services
e. Safety Data Business Process Improvement and Optimization Support Services
f. Safety Data and Information Communications and Data Delivery Support Services
C.4 RSIMSS Objectives
C.4.1 The RSIMSS will enable FRA to achieve the following objectives:
C.4.1.1 Advance the railroad safety data management program to meet current and future safety data and information needs of the inspection, enforcement, compliance, accident/incident, and grade crossing inventory regulatory requirements
C.4.1.2 Provide comprehensive regulatory support for maintaining current and future safety data collection requirements and developing and implementing new regulatory data requirements
C.4.1.3 Support operational and business process updates to maximize efficiency, safety data quality, safety data analysis, and information availability
C.4.1.4 Ensure the best practical and cost-effective technology tools are applied to meet FRA’s current and future safety data management and analysis needs, through a continuous improvement process
C.4.1.4 Ensure uninterrupted FRA safety data mission delivery to the FRA data stakeholders and citizens
C.4.1.5 Ensure proper maintenance of the RSIS data management programs and tools and providing transparent input to FRA’s change management processes, investment lifecycle processes, and security processes
C.4.2.The target RSIS state can be defined with three main goals, which are supported by the
RSIMSS:
C.4.2.1 Data Integration – Implement an integrated data structure to support and streamline reporting and analysis
C.4.2 2 Data Collection and Quality – Implement data validation and data quality checks at the point of entry to ensure valid and consistent data for internal FRA inspection and investigation reporting as well as external stakeholder data reporting
C.4.2.3 Data Distribution – Streamline the data distribution and delivery process and provide more valuable information to external and internal stakeholders and user groups to include
Application Programming Interfaces (APIs) and other data delivery provisions
C.5 Tasks
The tasks are divided into four contract line items (CLINs) as follows:
a. Data Collection, Data Processing, and RSIS Data Solution Operations and Maintenance, which will be activated at the time of contract award as a FFP task order.
b. Non routine maintenance, system development and enhancements, which is a CLIN structured for procuring these services in a flexible manner using FFP, LH or any combination thereof for task orders.
c. Transitioning In, which will support the transition of tasks to a new contractor or FRA as required.
d. Transitioning Out, which will support the transition in support of the termination of the contract.
C.5.1 CLIN 00001 – Data Collection, Data Processing, and RSIS Data Solution
Operations and Maintenance Objectives
The scope of CLIN 00001 is to procure, on a FFP basis, contractor services to manage the collection, acceptance, validation, entry, processing, storing, and publishing of all railroad safety data and to perform day-to-day data management, operations and maintenance activities required to ensure the data management solutions that are integrated with and enable the data collection and processing activities are maintained and functioning efficiently.
C.5.1.1 Management Objectives
The management objectives of CLIN 00001 are to:
1. Enable the contractor maximum flexibility to innovate, identify and propose the data management process and solutions to manage program performance, cost, and risk and deliver an effective and affordable RSIS which, Maintain clear government visibility into program cost, schedule, technical performance, and risk
Continually re-evaluate program effectiveness and provide periodic recommendations to the government for efficiencies that can be gained through process optimization and technology integration
Support the government with regulatory requirement gathering and provides data solution recommendations to meet those requirements
C.5.1.2 Technical Objectives
The technical objectives of CLIN 00001 are to:
1. Collect and distribute railroad safety data
2. Enable transparent and open data exchange (i.e. an API first approach) with FRA stakeholders including the public, industry, and other government agencies and bodies
3. Align data management processes and solutions with the DOT and FRA data management strategy
4. Continuously propose and improve the operational efficiency of the data collection and data management solutions encompassed within the RSIS program
5. Comply with Federal, DOT, and FRA requirements
C.5.1.3 Performance Objectives
C.5.1.3.1 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.
C.5.1.3.2 Project Visibility Objectives
The objectives are to enable government insight into program performance through (i) clear and concise work breakdown structures; (ii) a regularly updated and integrated project plan measured against the baseline; (iii) utilize generally accepted best practice management reports to identify potential schedule risks and cost overruns; and (iv) status reports with issues, risks and mitigation strategies.
C.5.1.3.3 Program Effectiveness Objectives
The objectives are to identify the overall effectiveness of the RSIS program in support of the
FRA safety mission and (i) identify gaps and propose improvements to the program to better support FRA’s safety mission and FRA’s stakeholders; (ii) support FRA when implementing program changes; and (iii) identify continuous process improvement.
C.5.1.3.4 New Regulation Objectives
The objectives are to pro-actively support the rulemaking process to identify RSIS program and solution impacts and (i) assess data and technical requirements of proposed rulemakings to identify impacts to RSIS; (ii) plan for updating the data collection process, data management tools, or data management solutions; and (iii) implement routine data management solution changes as part of this task or support the government with determining cost, scope, and schedule for any larger changes to be performed as an RSIS enhancement under CLIN 00002.
C.5.1.3.5 Data Collection Objectives
The objectives are to promote railroad safety through the following: (i) collect, assess, manage, and report on safety data; (ii) enable FRA to determine the effectiveness of safety programs through data availability and quality to support an overall reduction in the number of train accidents and incidents per million train miles; (iii) provide timely distribution of railroad safety data to FRA management, government agencies, railroad labor and management, and the general public; (iv) provide data resources to interfacing programs, such as National Inspection
Plan (NIP), and to support a valid statistical method of determining which highway railroad crossings are eligible to receive funds to improve warning systems; (v) record enforcement actions on regulatory violations and identify leading causes of accidents and injuries; (iv) support the determination of systemic problems (both self-reported and those reported by
Federal and state inspectors) and defective conditions of the railroad system; and (v) track and report on industry defect remediation activities.
Safety data includes accident data, incident data, highway-rail grade-crossing inventory data, operational data, inspection data, violation data, investigation data, other railroad safety regulatory and non-regulatory data and plans, etc.
C.5.1.3.6 Data Exchange Objectives
The objectives are to enable open, transparent, and two-way data exchange with FRA stakeholders including DOT and Modes, Railroad and related industries, other federal agencies, state and local governments, and citizens as determined appropriate by FRA. The objectives include (i) providing railroads with a secure method to access FRA inspection and violation data for railroads to track and remediate deficiencies; (ii) providing the public with a method to access railroad safety data including accidents and incidents, and highway-rail crossing data;
(iii) providing the capability to run dynamic queries, download railroad safety data, and view current statistical information on railroad safety; (iv) providing FRA and state partners a secure method 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.
C.5.1.3.7 Process Effectiveness Objectives
The objectives are to identify efficiencies in the process, tools, or solutions used over the duration of this task to achieve cost or performance efficiencies and (i) implement process efficiencies transparent to the data reporting or data users; (ii) recommend technology or user-impacting process changes for government consideration; and (iii) support regulatory process with information and analysis justifying those changes.
C.5.1.3.8 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,
(ii) align and support the FRA Enterprise Architecture (EA) policies consistent with the Federal
Enterprise Architecture reference models; and (iii) align and support the DOT and FRA Data
Management Strategy.
C.5.2 CLIN 00002 – Non-routine Maintenance, System Development and Enhancement
Services Objectives
Consistent with the scope and purpose of the contract, the contractor shall provide a full and complete range of technical and professional support to FRA to assist with any and all aspects of non-routine maintenance, system development and enhancement services. The contractor shall coordinate, and at times collaborate, with FRA Office of Information Technology to ensure any solutions align to FRA and DOT IT strategy, architecture, and security for deployment on
DOT’s network. Any new maintenance requirements, as the result of enhancements, will be covered under this CLIN until conclusion of the current contract period, at which time this maintenance will be covered under CLIN 00001 for the following contract period.
C.5.2.1 Safety Data Management Support Services
The following are objectives of the Safety Data Management support services:
• Modernize, enhance and develop data solutions, documentation, configuration management and testing in accordance with industry best practices and FRA/DOT policy with increasing efficiency and cost effectiveness
• Support changing mission needs, regulatory requirements, analysis requirements, or realize efficiencies by performing requirements analysis, supporting the regulatory process, identifying opportunities, and enhancing data solutions or tools accordingly
• Increase the program performance by utilizing modern methodologies and an API-first approach to effectively and efficiently implement enhancements or new solutions
• Perform complete requirements documentation, implementation, and testing in accordance with industry best practices and FRA/DOT policy and in alignment with the chosen methodology for any approved or procured enhancements
Data management tools and solutions in support of the data collection process, spans various languages and platforms may include .NET, SQL, SQL Server, PL/SQL, SAS, Visual Basic, JQuery, SharePoint, Java, Javascript , C++, AJAX, HTML, HTML5, CSS3, XML, JSON, ODATA, SOAP, REST, ESRI, ArcGIS Server, API’s, data modeling, Oracle 11gR2 database, Oracle Web Server 10g, JavaServer Pages, Struts, Oracle 10g Developer Suite for case generation reports, Redhat Linux Enterprise 7, and other modern languages for application maintenance activities. Note: the servers on which the databases reside are managed and maintained by FRA. The contractor will have to follow the FRA Change Control Board process.
C.5.2.2 Data Collection Support Services
The regulation and focus of FRA safety data collection changes over time as the rail industry operations and technology and safety trends are adopted. FRA has a requirement to be able to implement changing regulation requirements or implement process efficiencies within the RSIS data collection and management processes. The objectives of the Data Collection Support
Services task area are to:
Provide support for changing or updating data collection processes as required based on changing FRA mission or regulatory requirements to include interfacing and communicating with railroad reporting officers, FRA and State inspectors, and other FRA stakeholders
Modify processes and perform data collection processing based on new requirements to include data acquisition, data validation, data quality assurance, exception reporting, data conversion, data distribution, data delivery, data availability, and process performance, tracking and reporting
During ongoing data management operational and enhancement efforts under this service area and other service areas, FRA expects the contractor to provide recommendations and opportunities for making the data collection process more efficient. A focus of these recommendations should be on business process improvements to achieve operational efficiencies, realize strategic initiatives, and implement new mission and regulation requirements.
C.5.2.3 Safety Data Management Program Planning Support Services
RSIMD is seeking to strengthen its safety data and safety related data planning functions and operations in meeting regulatory and safety mission requirements. Strategic planning is an organization’s process of defining its strategy or direction and making decisions on allocating its resources in pursuit of this strategy, including both capital and people. The FRA is currently undergoing an enterprise data management assessment and will be issuing a data management strategy. The objectives of this service area are to:
Support FRA strategic goals by ensuring the RSIMSS program aligns RSIS with those programmatic and strategic goals and objectives
Support the alignment of RSIS to goals and objectives in DOT’s and FRA’s enterprise data management strategies
Provide a broad range of technical and professional services to support Office of
Railroad Safety’s data management program planning function and operations
Provide support and analyses, evaluations, strategic recommendations, and recommendations for plans of actions to assist in identifying and articulating strategies for achieving FRA’s safety data priorities; assess safety data management maturity and provide recommendations to develop an action plan to meet mission needs and adopt future data management trends, and providing advice on the implications of implementing new trends or tools with a focus on open source, cloud-based, or low/no-code solutions aligning to the White House’s Open Government Initiative
Enhance RSIMDs strategic and program planning for safety data management programs including program performance, developing plans and roadmaps for RSIMD safety data management business and technical architectures that conform to mission goals, transform the RSIMD organization, and align to acceptable risk tolerance
Enhance RSIMD’s analytical capability through performing scenario and trend analysis, performing cost-benefit analysis, and supporting the development and implementation of the data management program plan and strategic plan
Provide support for all regulatory mandate initiatives involving safety data
The contractor shall be knowledgeable of, and experienced in, applying data management and planning best practices to the public and private sector. In researching, assessing, and planning for new solutions and techniques, the contractor shall perform, obtain, and use long-term strategic assessments, projections, and trend analysis. The contractor shall map out possible outcomes for implementation and analyze their impact on the needs and capabilities of FRA to better use its data assets.
C.5.2.4 Data Distribution and Data Analysis Support Services
RSIMD provides stakeholders with safety data using various distribution and delivery methods and also provides data reporting and analysis for internal and external stakeholders. This data analysis can be delivered in various ways either through the creation of an ad-hoc report to a more permanent data delivery web-based query for those reports with more frequent requests.
As a result, RSIMD is seeking contractor support for enhancing and complementing its data distribution and data analysis functions. The objectives of the Data Distribution and Data
Analysis service area are as follows:
Support the alignment of FRA’s safety data assets to changing mission priorities, establishment of a flexible platform supporting FRA safety data analysis activities, and the performing of data analysis to provide safety information to FRA safety data stakeholders
Provide expertise and support to mature the RSIS analytical capability beyond trends analysis, based on historical data, with an objective of enabling predictive analytics and risk indicator analysis
Providing support for the transforming, merging, processing, and making available data for use in data analysis activities through updates to reports, capabilities, features, functions, and data integration to make the data more useful, more easily accessed or analyzed, and more capable
The contractor shall have experience with modern data analysis tools including graphical visualizations, dashboards, data mashups, and other techniques for communicating complex information in simple and easy to understand reports. The contractor shall be familiar with the state-of-the-art and understand industry best practices to provide recommendations for the appropriate tool or technique for the requested outcome and have experience performing alternatives analysis and business case analysis to back up the recommendation.
C.5.2.5 Safety Data Business Process Improvement and Optimization Support Services
The RSIMD safety data collection process is largely constrained by current Federal Regulation, however there are a number of processes to ingest, validate, process, store, and publish various pieces of safety data, which encompasses the full data management lifecycle. The objectives of the Safety Data Business Process Improvement and Optimization service area are as follows:
Support FRA with expertise in business process analysis, improvement, and optimization for assessing the as-is safety data business processes, defining to-be safety data business processes, performing gap analyses, and identifying roadmaps for achieving the to-be safety data business process design
Identify and implement performance metrics for RSIMD data management programs and operations to measure process effectiveness, program performance, and operational efficiency
Identifying efficiency, capability, and automation opportunities for existing safety data business processes and assessing required process, organizational, and technology changes for suitability for FRA’s safety culture, risk tolerance, and cost-benefit ratios
Implement safety data process improvement changes and monitor performance improvement
The contractor shall have experience with data management, customer interface, change management, and business process re-engineering and should be familiar with modern workflow and automation tools that may be implemented as part of the process improvement effort. The contractor shall be able to discuss detailed cost-benefits of the process changes, risks associated with making and not making changes, and analysis of alternative options.
C.5.2.6 Data and Information Communications and Data Delivery Support Services
An important aspect of the FRA safety mission is stakeholder outreach and communications.
The contractor shall provide a broad range of technical and professional services to support
FRA safety data communications. The objectives of the Data and Information Communications and Data Delivery service area are as follows:
Planning, analyzing, designing, developing, implementing, and managing communications strategies, plans, products, tools, and services
Engaging with internal FRA stakeholders in a persistent manner and position RSIMD to have an active presence in the FRA and DOT data management community through the coordination and scheduling of meetings and communications activities
Managing, developing, and publishing safety data and other communications assets
Increasing the reach of FRA safety data to internal, industry, state, and other stakeholders through more active communications campaigns
The contractor shall have experience with data distribution and data delivery, communications, internal and external marketing and user engagement, developing communications plans and assets, and developing language and graphics suitable for electronic publishing accounting for accessibility constraints (i.e. Section 508 and WCAG 2.0 compliance) on FRA safety data sites.
C.5.2.7 Required Expertise
The contractor shall demonstrate experience in each of the above capability areas. Additionally, the contractor shall demonstrate:
The ability to work with customers to assess needs, provide assistance, resolve problems, and satisfy expectations
Knowledge of safety programs; safety data management, analysis and use; FRA programs and mission; methods, metrics, tools, technology, and techniques for business process improvement and data management
Understanding of principles, methods, or tools for maintaining data management solutions, enhancing existing data management solutions, and developing new data management solutions
Understanding of methods and tools for managing projects and programs using various project management methodologies
Understanding of information assurance, cybersecurity, privacy policies, records management, and best practices
Understanding of White House and OMB initiatives related to open data, digital government, IPv6, and other relevant initiatives
C.5.3 CLIN 00003 – Transition In Support Services
The successful contractor shall conduct a complete turnover with the incumbent contractor. The government anticipates that one (1) month will be required. Turnover shall include all government furnished information, government data, and government furnished equipment (as required.) This shall occur under the direction of the COR to ensure a seamless transition of all services for the entire RSIS and subsystems.
C.5.3.1 Phase-In
The Contractor shall begin the transition phase-in at the start of the contract; however, the
Contractor has the option to begin the phase-in transition sooner at no cost to the Government, provided the contract is awarded. During this transition period, the Government will make available to key incoming Contractor personnel, a Government representative familiar with the operations and functions to be performed in relation to security systems operation, maintenance and technical support services. The Contractor shall become familiar with the contract requirements in order to commence full performance on the Contract Start Date. All work covered by this contract that was started but not completed by the Government or its Contractor by the Contract Start Date, shall become the complete responsibility of the Contractor for continuity of service.
C.5.4 CLIN 00004 – Transition Out Support Services
C.5.4.1 Phase-Out
To ensure a smooth transition to the successor Contractor and to prevent possible decreases in productivity or service quality, the Contractor shall, up to 30 calendar days before contract termination date, furnish phase-in training. During this period, the Contractor shall make available to key incoming Contractor personnel, a representative of the incumbent Contractor that is versed in the operation of the functions to be performed. The incumbent Contractor shall provide required training and transfer material, equipment, and/or tools as required by the existing and/or new contract. The incumbent Contractor shall conduct joint inventory with the
Government representative(s) and representatives of the incoming Contractor.
C.6 Management and Staffing
The contractor shall appoint an RSIMSS Project Manager (PM) and Deputy PM who interface directly with the Contracting Officer’s Representative (COR) and the RSIS System Owner to ensure that work requirements are met on schedule and that the Contractor produces accurate/quality products as efficiently as possible. The PM will be directly involved in all aspects of contract management and personal interactions with government staff are expected.
The PM will regularly review and communicate, at all stages, the progress or status of contract and task order items with the COR and RSIS System Owner to ensure adequate delivery and quality.
C.6.1 Policies and Procedures
Contractor personnel must adhere to current and future Government policies and procedures in the performance of their duties. These policies and procedures include: Standard Operating
Procedures, Security Policies, Project Management Life Cycle Methodology, Systems
Development Life Cycle Methodology, etc. All liability will rest with the contractor personnel.
C.6.2 Key Personnel
Key Personnel and/or facilities may be designated on a Task Order basis, with the exception of the PM and deputy PM. All personnel considered “Key” must be specifically designated as such in the executed TOs. All key personnel are subject to approval by the COR and/or System
Owner.
C.6.2.1 Project Manager (Key Personnel)
At a minimum, the project manager must:
Be able to demonstrate successful prior government consulting experiences in providing guidance and direction in resolving complex program management and organizational problems
Possess a Project Management Institute (PMI) Project Management Professional (PMP) or International Association of Project and Program Management (IAPPM) Certified
Project Manager (CPM), a minimum of 10 years of experience, with a minimum of 5 years managing a project of similar size, scope, and complexity
Experience in application development projects and data management projects
Exhibit capabilities in achieving objectives and solving problems in creative, resourceful, and innovative ways
Experience working with senior government executives to identify and recommend organizational goals, and how to achieve the goals by using various methodologies and technologies
Demonstrate innovative ways to resolve stakeholders’ conflicting requirements
Demonstrate capability to provide a complex solution that is flexible enough to accommodate changes in technology
Identify existing or emerging technological challenges to satisfy mission goals and objectives
Provide strategic planning and guidance on the evolution of business processes and system architectures, and the adoption of new technologies
C.6.2.2 Deputy PM (Key Personnel)
The deputy PM assists the PM in managing day-to-day contracting activities, will oversee the daily operations, and be able to back fill in the event the PM is unavailable. At a minimum, the deputy PM must:
Possess a minimum of 3 years of experience managing projects (PMP or CPM preferred, but not required)
Experience in application development projects and data management projects
Exhibit capabilities in achieving objectives and solving problems in creative, resourceful, and innovative ways
Experience working with government clients to gather requirements, establish goals and manage delivery
Demonstrate innovative ways to resolve stakeholders’ conflicting requirements
Demonstrate capability to provide solutions based on changing needs
C.6.3 Staff Performance/Replacement
1. The contractor shall provide a resume for each candidate proposed as key personnel on the IDIQ and any Task Order proposal
2. Proposed key personnel are tied to contract and task order award
3. The Government reserves the right to judge the technical skill and competence of the individual and to require the individual’s replacement if the individual’s qualifications or performance are judged to be deficient at any time with written notification to the
Contractor
4. The Government reserves the right to judge the qualifications and acceptability of any individual proposed by the Contractor for any positions, and may require the Contractor to replace an individual whose qualifications and suitability are judged to be deficient with written notification to the Contractor
5. The Contractor agrees the performance of work and services pursuant to the requirement of this contract shall conform to high professional and ethical standards.
The Contractor also agrees to remove any employee whose conduct or performance is such that retention would not be in the best interest of the Government as determined by the Project Officer, COR and Contracting Officer
C.6.3.1 Government Furnished Equipment (GFE) and Asset Requirements
At FRA discretion, the incumbent, under direction of FRA, will transition any government furnished equipment and the entire source codes to the winning contractor. The contractor will provide an equipment transition plan within 90 days to FRA, detailing how they will transition from GFE to contractor owned equipment within 6 months of contract award. Virtual Desktop
Infrastructure (VDI) accounts will be provided by FRA to the contractor’s staff who require access to the DOT network. The offerors shall propose the number of personnel they believe will require DOT VDI access. Workstations may be provided on an as-needed basis to those staff that may require specific client applications or otherwise where VDI alone is insufficient to perform the requirements of the SOO. The offerors shall propose the number of personnel they believe will require DOT provided workstations.
The figure below demonstrates the current separation of equipment and environments (provided for reference). In addition, the FRA environment also contains a test environment for testing applications prior to deployment to staging or production.
Figure 1: RSIS Environment Separation
The FRA shall retain ownership of all Government Furnished Property (GFP) assets (hardware, software, data, specifications, code, and tools) covered in the scope of this contractor. All code is and will remain the property of the FRA. The FRA retains the right to determine IT standards, including refreshed equipment. The Contractor shall make every effort to leverage existing FRA hardware and software agreements, if it is in the best economic interest of the FRA.
Railroad Data Reporters
APPENDIX A
Table of Acronyms
Acronym Definition
AF Activation Failure
AIRGNET Accident/Incident Report Generator
API Application Programming Interface
ATIP Automated Track Inspection Program
BI Business Intelligence
BSA Block Signal Application
CCB Change Control Board
CISP Critical Incident Stress Plan
CMS Content Management System
COR Contracting Officer’s Representative
CPIC Capital Planning And Investment Control
CWR Continuous Welded Rail
DB Database
DOT Department of Transportation
DR Disaster Recovery
EA Enterprise Architecture
EST Eastern Standard Time
ETL Extract, Transform, and Load
FAR Federal Acquisition Regulation
FARS Factual Accident Incident Reporting System
FFP Firm Fixed Price
FIPS Federal Information Processing Standards
FP False Proceeds
FRA Federal Railroad Administration
GB Gigabyte
GCIS Grade Crossing Information System
GFE Government Furnished Equipment
GIS Geospatial Information Systems
GPRA Government Performance and Results Act
GSA General Services Administration
HQ Headquarters
IaaS Infrastructure as a Service
IAR Inspector Activity Report
IDIQ Indefinite Delivery, Indefinite Quantity
LH Labor-Hour
NIP National Inspection Plan
ODC Other Direct Costs
OLAP Online Analytical Processing
ONS Office of National Statistics
OTMA One-time Movement Approval
PIV Personal Identification Verification
PM Project Manager
POAM Plan of Action and Milestones
POC Point of Contact
QZC Quiet Zone Calculator
RAIRS Rail Accident/Incident Reporting System
RES Railroad Enforcement System
RIP Regional Inspection Point
RIRS Railroad Inspection Reporting System
RISPC Railroad Inspection Program for the PC
RR Railroad
RRS Office of Railroad Safety
RSIA Rail Safety Improvement Act
RSIMD Railroad Safety Information Management Division
RSIMSS Railroad Safety Information Management Support Services
RSIS Railroad Safety Information System
RSO Railroad System Oversight
RSOM Railroad System Oversight Manager
SAM Staffing Allocation Model
SME Subject Matter Expert
T&M Time and Materials
TO Task Order
VGTS Violation Generation and Tracking System
WBAPS Web-based Accident Prediction System
WCAG Web Content Accessibility Guidelines
XML Extensible Markup Language
END OF SECTION C
SECTION D - PACKAGING AND MARKING
D.1 PRESERVATION, PACKAGING AND PACKING
(A) Packaging and marking of all deliverables shall be in accordance with the best commercial practice necessary to ensure safe and timely delivery at destination, in accordance with the applicable security requirements.
(B) All data and correspondence submitted to the Contracting Officer (CO) or the Contracting Officer’s (COR) shall reference the contract number, and the name of the Contract Specialist as appropriate.
D.2 INITIAL PACKING, MARKING, AND STORAGE OF EQUIPMENT
All initial packing, marking and storage incidental to shipping of equipment to be provided under this contract shall be made Freight on Board Destination (FOB Destination) at the contractor’s expense. Such packing, supervision marking and storage costs shall not be billed to the Government. Supervision of packing and unpacking of initially acquired equipment shall be furnished by the contractor.
D.3 MARKING
Packages shall be clearly marked as follows:
(1) Name of Contractor;
(2) Contract Number and Task Order Number as applicable
(3) Description of Items Contained Therein; and
(4) Consignee’s Name and Address.
END OF SECTION D
SECTION E - INSPECTION AND ACCEPTANCE
CLAUSES INCORPORATED BY REFERENCE (FEB 1998)
This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. Also, the full text of a clause may be accessed electronically at the below address:
HTTPS://WWW.ACQUISITION.GOV/FAR/
(End of clause)
NUMBER TITLE DATE
52.246-4 INSPECTION OF SERVICES- FIXED PRICE AUG 1996
52.246-6 INSPECTION-TIME-AND-MATERIALS AND
LABOR-
LABOR-HOUR
MAY 2001
E.1 INSPECTION OF SERVICES
(A) The Contracting Officer (CO), or his duly authorized representative, is authorized to perform inspection on behalf of the Government for the purpose of acceptance of all services to be provided. In this regard, the Government Contracting Officer’s Representative (COR) is an authorized technical representative of the Contracting Officer. Final acceptance of all services under this contract shall be made in writing by the COR designated in writing by the Contracting Officer.
(B) The COR listed in Section G has been delegated authority to inspect and accept all services, reports and required deliverables or outputs for the base contract. The Government will review and accept all deliverables within 10 calendar days.
(C) A task order COR (TO COR) may be established for a specific task order or task orders.
The TO COR may inspect and accept all services, reports, and required deliverables or outputs if specified in the task order.
E.2 INSPECTION AND ACCEPTANCE
(A) On an ongoing basis, Government personnel shall conduct inspections of the contractor’s work, primarily utilizing the method identified under this contract and task orders issued against this contract.
(B) Government inspection and acceptance of services, reports and other required deliverables or outputs shall take place at the Government’s site identified in the contract and task orders.
END OF SECTION E
SECTION F - DELIVERIES OR PERFORMANCE
CLAUSES INCORPORATED BY REFERENCE
NUMBER TITLE DATE
52.242-15 STOP WORK ORDER AUG 1989
52.242-17 52.247-34
GOVERNMENT DELAY OF WORK
F.O.B. DESTINATION
APR 1984
NOV 1991
F.1 PERIOD OF PERFORMANCE
(A) Base Period of Performance: The period of…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .