|
|
SAFER release schedule for FY06
|
| CR Number: |
|
67 |
| External Reference: |
|
|
| Category: |
|
SAFER |
| Component: |
|
Database |
| Change Status: |
|
12. Confirmed |
| Synopsis: |
|
Oracle 10g upgrade |
| Description: |
|
The database server will be upgraded to using Oracle 10
g RAC.
All SAFER application components will need to be testing with Oracle 10g
server.
Modification to the program will be made when necessary.
SAFER database migration will be coordinated with MCMIS, L&I, and PRISM.
The migration completed successfully on 11/15/2005.
|
| CR Number: |
|
139 |
| External Reference: |
|
CVISN CR#3013 |
| Category: |
|
SAFER/CVIEW |
| Component: |
|
SAFER XML, SAFER ICD |
| Change Status: |
|
3. Pending |
| Synopsis: |
|
Standardization of data values in XML input transactions |
| Description: |
|
When searching data against the SAFER database, it has
brought to our attention that some key data fields submitted from the XML input
transactions are provided in an inconsistent manner.
A good example is that the IRP_ACCOUNT_NUMBER in T0020 can have leading zeros,
leading space and etc. Another example is IRP_CARRIER_ID_NUMBER OR
CVIS_DEFAULT_CARRIER in T0022 where leading zeros and null can be an issue to
CVISN or PRISM states.
This CR is intended to standardize the data format of the input data fields and
perform edit checks or validation on key fields like IRP account number and
VIN. The result of this effort shall improve the overall e-credential data
integrity and data quality of the SAFER database.
The Volpe Centerhas performed technical analysis on all XML input transactions
and the SAFER database. Based on the analysis, the data requirements was
summarized in the spreadsheet that has been discussed by the ACCB. Volpe has
put together the data specification for the requirements gathered by the
stakeholders. The specification together with standards for VIN validation, IRP
account, IFTA account have been posted to the CVISN LISTServ. The ACCB has
approved the CR for implementation and this will be part of the SAFER version
5.0 to be released at the end of February 2006. A summary of implementation and
requirements for recertification has also been sent to the LISTServ.
|
| CR Number: |
|
431 |
| External Reference: |
|
|
| Category: |
|
SAFER /CVIEW |
| Component: |
|
SAFER company snapshot, SAFER XML sendlist |
| Change Status: |
|
3. Pending |
| Synopsis: |
|
Carrier snapshot changes to include Inspection count for
the over size/over weight commercial vehicles to the company snapshot shot and
distribute via T0031 V2 transaction and HM permit data |
| Description: |
|
Louiseana has requested to add the reords count for the
over size / over weight commercial vehicles inspected during the 24 months
period to the T0031 transaction.
This will requires MCMIS to calculate the count and modify the materialized
view to include the inspection count. Once MCMIS modifies the program. SAFER
load will be changed accordingly.
ACCB meeting has approved this CR for FMCSA consideration in 09/2005. FMCSA has
requested to add HazMat permit data to the company snapshot in the future
release. This CR has been approved by FMCSA to be implemented in FY 2006. |
| CR Number: |
|
486 |
| External Reference: |
|
|
| Category: |
|
SAFER/CVIEW |
| Component: |
|
SAFER web services |
| Change Status: |
|
3. Pending |
| Synopsis: |
|
Expand SAFER web services to other XML transactions to
support CVISN users. This includes the six input transactions and five other
output transactions that SAFER interacts with the CVIEW |
| Description: |
|
This CR is an extension of CR 21 that has been
implemented in SAFER version 4.4. The SAFER web services implemented in CR21
provides query function for the CVIEW states to retrieve information directly
from SAFER when data is not available in the local CVIEW system. This function
is available for T0028, T0031 and T0032. This CR will apply web services
technology to all transactions. Because of the scope of the enhancement,
implementation of web services to other five output transactions will occur in
SAFER version 5.0. The implemenation of web services to the input transactions
will be made in SAFER version 5.1 in August 2006. |
| CR Number: |
|
435 |
| External Reference: |
|
|
| Category: |
|
SAFER / MCMIS |
| Component: |
|
SAFER web |
| Change Status: |
|
3. Pending |
| Synopsis: |
|
Develop an service to automatically post message on the
SAFER web site |
| Description: |
|
FMCSA and MCMIS team has requested SAFER team to
implement a service, which will automatically post message to the SAFER web
home page to report the operation status of the FMCSA pay.gov service.
The benefit of this service is to improve the communication among FMCSA,
technical staff and the end users in time of the service failure, downtime and
performance slowness. It will ultimately help managing users' time more
effectively.
The SAFER team is working with the MCMIS team to define the functionally
requirements and scope. The design documentation has been reviewed and approved
by the FMCSA program managers. This will be implemented in the SAFER release
5.0 in February, 2006.
|
| CR Number: |
|
498 |
| External Reference: |
|
|
| Category: |
|
SAFER/PRISM |
| Component: |
|
|
| Change Status: |
|
3. Pending |
| Synopsis: |
|
Enhance PRISM MCMIS update validation routnine. SAFER
needs to validate the PRISM .dll during the ELQ MCMIS update to ensure this is
backwards compatible with the MCMIS load application |
| Description: |
|
This CR is created in response to PRISM's SAFER Support
Request Tasks Overview Ref#7 to enhance the PRISM MCMIS update validation
routine.
PRISM.dll runs during ELQ MCMIS update has been updated by the PRISM team.
SAFER team needs to run acceptance test before it is deployed into production.
This CR is ranked as medium and low severity to the PRISM program and is
considered to be implemented in SAFER version 5.0 in February 2006.
|
| CR Number: |
|
526 |
| External Reference: |
|
|
| Category: |
|
SAFER/MCMIS |
| Component: |
|
SAFER MCMIS load and SAFER web |
| Change Status: |
|
3. Pending |
| Synopsis: |
|
Support the new insurance check box value from CAPRI and
ASPEN |
| Description: |
|
FMCSA has requested to add insurance verification check
in the inspection upload processing. SAFER will work with ASPEN, SAFETYNET and
MCMIS to make consistent changes to the program in the February release. |
|
