FILE | D | Classification Management Solution - RFI

FBO DAILY ISSUE OF NOVEMBER 16, 2008 FBO #2547
DOCUMENT

D -- Classification Management Solution - RFI

Notice Date: 11/14/2008
Notice Type: RFI
NAICS: 541511 — Custom Computer Programming Services
Contracting Office: Department of the Air Force, Air Mobility Command, Headquarters AMC Contracting, 402 Scott Drive, Unit 2A2, Scott AFB, Illinois, 62225-5320, United States
ZIP Code: 62225-5320
Solicitation Number: AFCA-EACO-0001
Archive Date: 12/30/2008
Point of Contact: joseph f brown,, Phone: 6192296712, joseph f brown,, Phone: 6192296712
E-Mail Address: joseph.brown.4@us.af.mil, joseph.brown.4@us.af.mil
Small Business Set-Aside: N/A
Description: OFFADD: AFCA/EAC, 203 W. Losey St, Rm. 1100, Scott AFB IL 62225-5200 SUBJECT: REQUEST FOR INFORMATION DESC: This announcement constitutes a Request for Information (RFI) synopsis. Information obtained as a result of this synopsis is for planning purposes only. It does not constitute an invitation for sealed bid or request for proposal (RFP), nor is it to be construed as a commitment by the government. The government is currently conducting a market survey and analysis of government-off-the-shelf and commercial off-the-shelf products that can meet the requirements for the vision of the Classification Management Solution (CMS). Sharing of information is critical to the defense of our nation. The DoD CIO stated in the DoD Information Sharing Strategy: "It is imperative to effectively exchange information among components, Federal agencies, coalition partners, foreign governments and international organizations as a critical element of our efforts to defend the nation and execute national strategy." Marking instructions, with appropriate declassification guidance, must therefore be current, accurate, and consistent with the Executive Order 12958, as amended. An enterprise classification marking solution for the United States Air Force (USAF) is a critical step to share information by providing properly marked and formatted information in either email or document form. This tenet is a primary building block in sharing information from one security domain to another, e.g., NIPRNET to SIPRNET, or SIPRNET to coalition network (CENTRIXS) and is documented in the Functional Solutions Analysis (FSA) for Multinational Information Sharing (MNIS). The Controlled Access Program Coordination Office (CAPCO) standard is identified as a starting point for establishing an internationally accepted marking standard for information objects. The vision of the CMS is to enable individuals to mark email and documents with little or no knowledge of regulatory marking standards. This capability would enable US and Non-US information sharing while allowing for future multi-level security technologies that rely on data tagging and document marking. Correct formatting of documents/email is critical in order to pass information from one security domain to another. Cross domain guards/rule sets may reject emails due to improper formatting. This solution would promote uniform, consistent, and comprehensive markings throughout USAF while enforcing USAF specific and CAPCO marking implementation guidelines. The solution would also protect information from potential unintentional declassification and/or distribution by ensuring classification banner/meta data accurately reflects the highest classification of a document denoted by portion markings and/or embedded data. USAF and CAPCO guidelines are very complex with many caveats. All documents/e-mails must include applicable header/footer banners, portion markings on paragraphs/e-mail subject lines, and declassification instructions. Declassification instructions, for example, come in two main forms which should be automated for the average user: originally and derivatively classified documents. An originally classified document has the "Classified By:", "Classification Reason:", and the "Declassify On:" instruction lines while a derivatively classified document only has "Derived From:" and "Declassify On:" lines. The resulting requirements are designed to fulfill this vision and, if followed, would yield the example below. Example of e-mail subject line: Example of marked document: Product submissions should attempt to provide the capabilities described in the CMS vision. Requirements for the CMS are centered around the following focus areas: 1) classification markings; 2) USAF environment; 3) guard/filtering interaction; and 4) user error mitigation. Attachment A includes a non-exhaustive list of requirements (RQMT) which stem from the afore mentioned CMS vision. The minimum set of requirements that must be successfully met prior to initial USAF deployment is classified as "level one" requirements, although incorporating as many of the other requirements into the initial release would be highly desired and encouraged. The requirements listed could be modified at any time after the RFI to reflect overall changes due to the current needs of the DoD and USAF, regulatory changes, and/or discoveries made during the RFI process, to enhance the requirements prior to any procurement effort. All requirements will be developed following the normal software development lifecycle process. Appendix B contains a list of guiding authorities which must be adhered to by any solution. Appendix C includes the definitions of key terms as used in this CMS RFI. Once again, due to new regulations being published, current regulations being updated and/or refined, and the changing needs of the USAF, all requirements are subject to change prior to initiating any procurement process. At a minimum, a vendor's RFI submission should answer the following questions: 1. How does the vendor's capability/concept support the CMS vision? 2. Can the vendor accurately relate customer definition of terms/concepts to vendor-specific solutions? 3. Does the proposed capability/concept rely on any proprietary standards to meet any of the requirements? 4. Does the solution meet the vision/requirements "as is" or is specific development required? 5. If development is required, is the vendor willing/able to accommodate an iterative process (e.g., the Unified Software Development Process) or does the vendor primarily utilize "waterfall" (AKA "all requirements first") approaches to software development? 6. How does the vendor deal with out-of-cycle requirements processing? 7. What is the timeline of completion, to include any development or deployment issues? 8. Does the vendor offer administrative/user support capabilities? 9. What are the expected cost breakdowns (e.g., development, licenses, "support" desk). 10. What warrants a version change over an interim change? 11. Does the vendor have any Microsoft Partnerships/Certifications? 12. Does the vendor's solution have any awards and/or relevant success stories/testimonials? Vendors responding to this RFI who currently can make solutions available to the USAF are requested to provide a description of capabilities NLT 30 days from publication of this notice. Potential vendors may express interest, make comments, and ask questions via electronic mail, phone call, or fax to the Air Force Communications Agency, Enterprise Architecture Planning at AFCA.EA.CSNI@scott.af.mil, (618) 229-6816, FAX (618) 229-5339. Vendors that meet USAF requirements will be allowed to schedule a demonstration, at no cost to the government, to highlight their solution's capabilities and provide software/concepts for USAF review. All comments and questions must be in writing and must identify the company source, contact person, e-mail address, and telephone number. EMAILADD: AFCA.EA.CSNI@scott.af.mil EMAILDESC: Air Force Communications Agency, Enterprise Architecture Planning, Scott AFB IL Appendix A - CMS Requirements Appendix B - Guiding Authorities for Email/Document Marking Appendix C - CMS Definitions
Web Link: FedBizOpps Complete View
(https://www.fbo.gov/?s=opportunity&mode=form&id=85abd25e9b26bc9db77f0eefbbba8e69&tab=core&_cview=1)
Document(s): RFI; File Name: This is the CMS RFI with figures included. (RFI_22Oct2008.doc); Link: https://www.fbo.gov//utils/view?id=d53da69d311dbc41fe2f8f8a939e6c67; Bytes: 959.00 Kb; File Name: Appendix A (Appendix A - CMS Requirements (23Oct08).pdf); Link: https://www.fbo.gov//utils/view?id=1c0cfccff1a20c6a62c516b25e6a2887; Bytes: 77.19 Kb; File Name: Appendix B (Appendix B - Guiding Authorities for Email_Document Marking (23 Oct 08).pdf); Link: https://www.fbo.gov//utils/view?id=70b49cde61fed99756dcd6c02e90cb5a; Bytes: 88.59 Kb; File Name: Appendix C (Appendix C - CMS Definitions (23 Oct 08).pdf); Link: https://www.fbo.gov//utils/view?id=53265a02538746499577e0fbda72c991; Bytes: 64.17 Kb; Note: If links are broken, refer to Point of Contact above or contact the FBO Help Desk at 877-472-3779.
Record: SN01704953-W 20081116/081114215837-85abd25e9b26bc9db77f0eefbbba8e69 (fbodaily.com)
Source: FedBizOpps Link to This Notice
(may not be valid after Archive Date)

| FSG Index | This Issue's Index | Today's FBO Daily Index Page |

Loren Data's SAM Daily™

D -- Classification Management Solution - RFI