In those cases where a legacy O/S cannot, or will not, be upgraded due to operational necessity or incompatibilities with program requirements, or the manufacturing process, the ISSM must submit the contractual requirements or the government customer must provide a letter (signed by the Contracting Officer, the Contracting Officer's Representative, the Contracting Officer's Technical Representative, or the Government Program Manager) stating there is a program requirement to use the legacy O/S and the GCA acknowledges the risk associated with its use. Individual IS POA&M entries must include specific activities necessary to provide an effective and timely transition to an operating system with continued vendor support at the time of reaccreditation. The IS Tracking Form may be found under the Downloads section of the ODAA webpage.Īdditionally, the ISSM must add an entry to each individual IS POA&M and submit to DCSA for approval prior to the facility's next SVA. Contractors will identify their plans in the remarks section of the IS Tracking Form. When information systems (IS) are accredited by DCSA and subsequently the O/S loses vendor support, continued operation IAW the SSP is authorized however, the contractor must submit an updated Information System Tracking Form to their respective ISSP, no later than 60 days from the date of this posting or the date of end of support, listing all the affected UIDs and documenting their plans for upgrade and/or providing Risk Acknowledgement Letters or contractual documentation language which requires the use of the legacy O/S.
What is DCSA’s position on continued use of operating systems which are no longer supported by the vendor, making them legacy operating systems?
0 kommentar(er)
