SOURCES SOUGHT
D -- Joint Verification System (JVS) and Enterprise Application Integration and Portal Services
- Notice Date
- 6/28/2010
- Notice Type
- Sources Sought
- NAICS
- 541512
— Computer Systems Design Services
- Contracting Office
- Defense Information Systems Agency, Procurement Directorate, DITCO-Scott, 2300 East Dr., Building 3600, Scott AFB, Illinois, 62225-5406, United States
- ZIP Code
- 62225-5406
- Solicitation Number
- BTA2010-01
- Archive Date
- 7/28/2010
- Point of Contact
- Melissa J Benhoff, Phone: 6182299142, Virginia A McCann, Phone: 618-229-9720
- E-Mail Address
-
melissa.benhoff@disa.mil, Virginia.McCann@disa.mil
(melissa.benhoff@disa.mil, Virginia.McCann@disa.mil)
- Small Business Set-Aside
- N/A
- Description
- 1. Purpose 1.1. The Defense Information System for Security (DISS) Program Office under the Business Transformation Agency (BTA) at the Department of Defense (DoD) seeks information related to the development of the Joint Verification System (JVS) and Enterprise Application Integration and Portal Services components of the Department's end-to-end security clearance process reform initiative. The objective of this initiative is to provide the Information Technology (IT) solutions and processes that will deliver high-assurance security clearance determinations in the least amount of time at the lowest reasonable cost. 1.2. In accordance with Federal Acquisition Regulation (FAR) 52.215-3, Request for Information for Solicitation and Planning Purposes (October 1997), this notice is for informational purposes only and does not constitute a solicitation or Request for Proposal. This notice is not to be construed as a commitment by the government to contract for services. THE GOVERNMENT DOES NOT INTEND TO AWARD A CONTRACT ON THE BASIS OF THIS RFI OR REIMBURSE ANY COSTS ASSOCIATED WITH THE PREPARATION OF RESPONSES TO THIS RFI. 1.3. Please mark any proprietary or confidential information as such in your response. Any segments of the RFI response that are marked proprietary will NOT be made available to the public or other private firms. 1.4. This RFI serves several purposes: 1) to inform the DoD about potential processes, tools and approaches for the new component of the department-wide, end-to-end security clearance process reform initiative; 2) to inform the DoD on the type and scope of work expected; and 3) to receive information and feedback on interest and capabilities of potential sources. 2. Sources Sought 2.1. This Sources Sought Synopsis is requesting responses to the following criteria from small businesses that can provide the required services under the North American Industry Classification System (NAICS) Code 541512. In addition to Small Businesses, this Synopsis is encouraging responses from qualified and capable Service Disabled-Veteran Owned Small Businesses, Veteran-Owned Small Businesses, Women-owned Small Businesses, HUBZone Small Businesses, Small Disadvantaged Small Businesses, Historically Black Colleges and Universities/Minority Institutions, Small Business Joint Ventures, Consortiums and Teaming Partners. This Sources Sought Synopsis is issued to assist the agency in performing market research to determine whether or not there are two or more qualified and capable Small Businesses to provide the aforementioned service. 2.2. Please note that personnel with current DoD Secret clearances (minimum) and specific personnel with current DoD Top Secret clearances will be required at contract award. Responses must demonstrate the company's ability to perform in accordance with the Limitations on Subcontracting clause (FAR 52.219-14). Interested small businesses meeting the small business standard of NAICS code 541512 are requested to submit a response to the Contracting Officer by the closing date of the RFI. Late responses will not be considered. Responses should provide the business's DUNS number and CAGE code and include a statement of self certification under the NAICS code. Additionally, responses should include recent (within the past three years or work that is on-going) and relevant experience (work similar in type, scope, and complexity) to include contract numbers, project titles, dollar amounts, and points of contact with telephone numbers where the responder performed the relevant work. Provide a list of the current contract vehicles your services may be procured from, to include the General Service Administration (GSA), Federal Supply Schedule (FSS) and any other government contract vehicle. Marketing brochures and/or generic company literature will not be considered. Not addressing all the requested information may result in the government determining the responder is not capable of performing the scope of work required. 3. Instructions to Vendors 3.1. Written responses should reflect the functional requirements and capabilities presented in this document. In addition, the written responses should provide a clear and concise explanation of how the vendor's solution (or suite of software) would apply in the context of the DISS RFI scenarios that are presented in Section 8 of this document. 3.2. Based on the government's review of the submissions, a subset of vendors will be invited to demonstrate their solution to the government. 3.3. The outcome of this RFI has no impact on any future acquisitions. The purpose of this RFI is information gathering only. The submissions for this RFI and the demonstrations will not preclude the vendor from responding to future acquisitions, either individually or as part of a team. 4. Background 4.1. The Intelligence Reform and Terrorism Prevention Act (IRTPA) of 2004 was written to address national security issues, including the security clearance process. In June 2007 the Office of Management and Budget (OMB) Deputy Director, in collaboration with the Director of National Intelligence and the Under Secretary of Defense for Intelligence, established the Joint Security and Suitability Reform Team (in the future referred to as the Joint Reform Team or JRT). The JRT charter is to reform the federal government suitability and security clearance processes. 4.2. In response to the IRTPA, the JRT developed a transformed process to provide further improvements to the suitability and security clearance process. The process was outlined by the JRT in the Security and Suitability Process Reform Initial Report, dated April 30, 2008, and provided a framework for an enterprise-wide, end-to-end process, supported by appropriate IT systems, to make hiring, credentialing, and clearance processes even more timely and efficient to meet IRTPA guidelines. The framework, depicted below, aligns suitability and security clearance processes, enabling the application of consistent standards across agencies, and the reciprocal recognition of investigations. This framework does not outline the security clearance process, but shows the focus areas addressed in the report. The focus areas highlighted in dark blue are to be addressed through the DISS program. Figure 1 4.3. The JRT has outlined that outdated technology and disparate business processes have affected the timeliness, quality and cost of the security clearance process. Problems with delays in the process have affected the government's ability to hire the right personnel and the industry's ability to begin new projects in a timely manner. 4.4. Security clearance reform is a top 20 presidential initiative and a top 10 priority for the DoD. The DISS Program was stood up to address the security clearance issues for the DoD. 5. System Description 5.1. The DISS Enterprise Architecture Solution is an Integrated Enterprise System.The future vision of DISS is to provide a set of enterprise services to expose, communicate, reuse, and share services, across the enterprise, supporting the "end-to-end" process. Figure 2 5.2 The Enterprise Data Stores Layer contains structured and un-structured data required to support the DISS Program. It contains all the transaction databases, the Integrated Data Store, Operations Data Store and the Data Warehouse. The actual implementation of the physical databases is encapsulated and data is only accessed via Application Program Interfaces. 5.3 The Enterprise Application Integration Layer contains all the application services housed by the various systems of DISS. The Enterprise Application Integration Layer contains the various support services required for the Enterprise to function. It provides capabilities such as Security Services, Utility Services, Data Services, SOA Foundation Services etc. 5.4 The DISS Portal presents a unified User Interface for the DISS Enterprise allowing access to the various systems inside of the DISS Enterprise. In the "To-Be" vision of DISS, the vendor will be responsible for developing the DISS Enterprise Portal layer, the Enterprise Application Integration Layer, and the JVS Services. The vendor will also be responsible for ensuring all components of the DISS solution are integrated into the final solution. 6. DISS Functional Requirements 6.1. The DISS architecture shall establish and maintain an integrated, secure overall capability into which appropriate data relevant to the granting, denial, or revocation of a security clearance or access pertaining to military, civilian, or government contractor personnel shall be viewed, tracked and accesses from all authorized investigative and adjudicative agencies. 6.2. DISS shall support functionalities to integrate information between existing DoD clearance tracking systems and other authorized and disparate investigative and adjudicative agencies into a single consistent and consolidate system view transparent to the end users. 6.3. The future DISS solution shall ensure the quality in all security clearance processes can be monitored, metrics can be measured, and results can be shared with the congressional oversight of clearance reform teams. 6.4. DISS shall increase a decision-maker's ability to ensure reciprocity of clearances as well as address the requirements below: • Provide near real-time, accurate and integrated security clearance investigative and adjudicative information. • Support efficient and effective resourcing and management of security clearance requirements. • Provide the ability to analyze and forecast security clearance information. • Support compliance with DoD security clearance policies. • Provide data warehouse capabilities. • Strengthen reporting ability. • Provide automated analytical tools for security clearance trend analysis and forecasting based on end-to-end historical data. • Support federate search for security clearance information queries. • Provide timely and consistent information as part of the DoD composite view that will allow decision-makers to make sound security clearance decisions. 7. Components of DISS 7.1. The DISS process will be supported by multiple IT systems, some of which currently exist, that address the processes of adjudicative case management, automated record checks, security clearance verification, enterprise application integration and portal services. 7.2. Existing Capabilities 7.2.1. Adjudicative Case Management is the process of rendering formal determinations regarding an applicant's eligibility for clearance. This process provides a framework for assessing an applicant's trustworthiness and fitness for a responsibility that could, if abused, have unacceptable consequences for the national security of the United States. 7.2.2. The capabilities essential for providing efficient and effective adjudication and quality assurance, with regards to JRT policy, include the following: Electronic Delivery: Electronic Delivery (e-Delivery) permits the electronic transmission of investigative case results from the Investigative Service Provider (ISP) to the DoD enterprise system for automated pre-screening of issues, e-adjudication, and human adjudication. Electronic Screening: Electronic Screening (e-Screening) uses a set of business rules to analyze an applicant's case packet to flag potential issues. This method compares the data from the Report of Investigation (ROI), to a set of pre-defined business rules to determine if a case contains discrepant information of concern; and flags potential issues pertaining to the investigation for Top Secret and Top Secret/Sensitive Compartmented Information (TS/SCI) clearance requests. Results of e-Screening are published to the adjudicator to be utilized during the adjudicative process. E-Screening also identifies cases with no actionable issues and sends them to be e-adjudicated. All other cases are routed to human adjudication. Electronic Adjudication: Electronic adjudication (e-Adjudication) is a viable technical means to automatically and electronically render hiring and clearing determinations in cases with no actionable issues. Today, approximately 25 percent of all Secret cases can be favorably e-adjudicated by applying computer coded business rules to the adjudicative decision process. Executive Order 13467 permits the use of "appropriate automated procedures" when determining security clearance eligibility with the Executive departments and agencies. It also allows for electronic messaging for human adjudicators to notify applicants, security managers, or other designated personnel of adjudication status or outcomes; provides cost and status tracking and provides a monitoring capability to attach hard-copy documents and allows posting and tracking of adjudicator training and certificates. Human Adjudication: Human adjudicators carefully evaluate the intricate details of each case and have the ultimate responsibility of rendering adjudicative decisions. The adjudicative capability within DISS allows an adjudicator to automatically apply the adjudicative guidelines to a ROI and render an adjudicative decision. Rapid Assessment of Incomplete Security Evaluations (RAISE): The RAISE solution is a stand-alone online quality tool that gathers specific information about the quality of Personnel Security Investigations (PSI) in order to provide quality reports to OPM and PAC. Upon completing a case in the adjudicative case management system, an Adjudicator logs into the RAISE system and provides feedback on the scope and/or information deficiencies found within the case. Feedback reports can be generated for a specific case or for aggregated data. Secure Telework: Provides secure remote access capability of centrally located adjudicative applications and information resources. Secure telework provides for increased productivity and allows the DoD agencies to remain responsive in performing adjudicative functions and reduces the probability of a breaching of Personal Identifiable Information (PII). 7.2.3. Automated Records Check (ARC) provides a fully-automated process to run applicant data against appropriate government and commercial databases to collect, analyze, and validate clearance data in order to produce reports that flag potential issues. This will provide consistency, as well as cost and time efficiencies for authorized investigating agencies and their ISP. System to System Access: Uses the applicant's background information to check against government and commercial databases to verify and identify issue information more efficiently. These additional sources of information assist in verifying identity and afford access to timely, robust, and ever-expanding sets of data that are critical to hiring and clearance decisions. Analysis of Collected Data: The ARC capability helps to verify that data integrity is upheld by flagging any inconsistencies between applicant information and the collected results. If results show discrepancies when compared against information provided by the applicant during the application process, issues are flagged to signify areas of potential concern. By identifying these areas of concern, ARC is able to support the succeeding adjudication and investigation processes. Report of Investigation: For each queried individual, a report can be produced in multiple formats. These reports can be machine-readable and used for automated lead scheduling by a case management system. The reports are also available in human-readable format and can be customized for users such as pre-screeners, investigators, or adjudicators. 7.3. New Capability Requirements Below are the capabilities we are requesting information on in regards to approach, design, etc. The capabilities listed are a starting point for items that should be included in the components but are not a comprehensive listing. 7.3.1. The Joint Verification System/Security Management (JVS) will provide security clearance verification by using applicant PII to check existing clearance. Functional requirements to be considered in development include: Repository for eligibility: Uses a database to collect as well as verify pertinent information to determine an applicant's eligibility. View of Determinations: Provides an approved list of security clearance determinations and eliminates the unnecessary processing of clearance applications for applicants who hold prior clearances investigations or adjudicative determinations. Virtual Security Management Office: Provides security managers with current clearance information and the ability to update a person's accesses and security history. Additionally, it determines what information an individual can access including assignment of user roles, based on a need-to-know basis. 7.3.2. The Enterprise Application Integration and Portal Services will provide the end-to-end capability for security clearance personnel e.g. adjudicators, investigators, security managers, to access data through a common access portal. The capability will be achieved through an integrated architecture approach. Key requirements include: External Interface Services • Legacy System Integration: Ability to for web-services to connect with legacy non-service based systems. • Protocol Adapters: Provide the infrastructure for data transmission protocols (HTTP, FTP, etc). SOA Foundation Services • Business Rules Management: Provides the ability to define, deploy, execute, monitor, and maintain the business decision logic that is used by DISS. • Business Process Management: Provides the ability to execute and monitor DISS business processes. Utility Services • Notifications and Alerts: Generates event, case, and time-based messages by providing notifications to appropriate users via emails and/or DISS Portal-originated notifications. • Logging: Includes portal activity log, services access log, and data access log. • Scheduling: Supports time-based event scheduling functions, such as the Continuous Evaluation (CE), a process through which current clearance holders are re-evaluated for clearance eligibility following a predefined period of time. Platform Services • Reporting: Provides reporting capabilities for the DISS enterprise. This includes standard adjudicative or re-investigative reports and the means for capacity planning. • Case Management: Provides the ability to manage all information relevant to a business work item, or case, and provides automated support for case workflow and associated business processes. • Records Management: maintains the records of DISS from the time produced up until their disposal. This may include classifying, storing, securing, and destruction (or in some cases, archival preservation) of records. • Capacity Planning: Provides the means to project the number of clearance investigations that will be required for future and current DoD, industry personnel. This will better enable the ability to project planning for workload and funding. • Content/Document Management: Supports the ability to upload documents and store the data in a central repository. • Case Tracking: Tracks an applicant's case throughout the security clearance process. This eliminates the potential for multiple security clearance applications to be opened for the same applicant and allows status checks to be produced for each stage of the process. Security Services • Role Based Access: Provides a role-based interface for adjudicators to central electronic repository of ARC, Expandable Focused Investigation (EFI) and Enhanced Subject Interview (EFI) results to access completed investigations or partial investigations with significant derogatory information and to post results of human adjudication required. • Encryption: Provides ability to encrypt and decrypt data. • Digital Signatures: Supports the ability to authenticate a digital message or document. • Data Services • Data Access: Provides the ability to create, read, update, and delete data. • Federated Search Service: Queries various databases to determine an applicant's existing clearance level. Compiled search results on the applicant are returned to the Agency system in one aggregated view where they are compared to the position description for eligibility determinations and to determine whether a new investigation is required for the applicant. 8. DISS RFI Scenarios 8.1. Purpose. The purpose of these scenarios is for a vendor to build a solution and demonstrate their ability to execute in a Service-Oriented Architecture environment and to identify software recommended to provide the functionality required by DISS. The solution will encompass three standalone systems exposing their web services to an Enterprise Application Integration (EAI) component. These services will be orchestrated via a business process. Business Rules will be stored in a Business Rules Engine. The Services will be registered in a Service Registry. The User Interface will be presented in a unified portal type solution. 8.2. Systems For the purpose of the following scenarios, the three systems encompassed by this solution are: • Clearance Management System • Visit Management System • Incident Management System • NOTE: These three "systems" represent the logical service components of JVS Services found in Figure 2. 8.3. System Requirements • Single Sign On across all three systems utilizing 2-factor authentication • Ability to grant an individual access to one or many systems • An integrated business process going across three systems • Messages will cross system boundaries utilizing web services • Ability to attach documents to visit requests and incident reports • Ability to manage work with standard workflows • Ability to change workflows on the fly during demonstration • All business rules developed by the vendor should be implemented in a business rules engine 8.4. Scenarios to be Demonstrated The following are representative business processes that may or not be implemented in the final solution. 8.4.1. Scenario Description: Create User An Account Administrator will log into the Clearance Management System and create a subject. The Account Administrator will assign a name, a clearance level, and a Security Management Office (SMO) to the subject. By default, the user will be assigned to the SMO of the Account Administrator. 8.4.2. Scenario Description: Visit Invite For each step of the process, the actor will be able to add additional comments. The system shall maintain an audit log of approvals and denials. 8.4.2.1. The Meeting Host will log into the system and create a meeting. Meeting attributes include meeting purpose, location, dates, security clearance required, and participants. *Assumption: Each person will have an existing record in the system. The system should be able to auto-populate person data. 8.4.2.2. A notification will go out to each of the meeting participants, directing them to log in to the system to fill out their remaining information and submit the meeting request to their Participant SMO. 8.4.2.3. The Participant SMO receives a notification of the meeting request. The Participant SMO logs into the system and verifies the participant's information. The system shall flag records where there are data mismatches or where the required clearance level for the meeting is not met by the participant. The Participant SMO can then reject or submit the visit request. A rejected visit will have the ability to have comments associated with it for view by the Meeting Host and/or Participant. 8.4.2.4. If rejected, the Meeting Host and the Participant will get a notification along with a reason for denial. The Meeting Host and/or Participant may resubmit a Visit Request. 8.4.2.5. The Meeting Host will be able to log in and check the progress of the visit requests. The Meeting Host will not be able to access PII or clearance data. The Meeting Host will then be able to send out additional Visit Invites, re-send Visit Invites to existing Participants, or submit the meeting request to the Hosting SMO. 8.4.2.6. If the meeting request is submitted, the Hosting SMO will receive a notification. The Hosting SMO will review the meeting request and approve or deny the meeting. The Hosting SMO will also be able to see the personal details of each of the participants and approve or reject specific individuals. Once the approvals and denials have been submitted, notifications will go out to all parties, as appropriate. 8.4.2.7. The gate guard will log into the system and be prompted with a list of each individual authorized to attend a meeting at this site for the particular day. 8.4.3. Scenario Description: Incident 8.4.3.1. This scenario is an extension of the Visit Invite scenario. This scenario assumes that a Participant has been approved for a visit that is scheduled to take place in the future. 8.4.3.2. An incident is logged into the Incident Management System for a meeting participant. 8.4.3.3. The system then flags the participant's record and sends a notification to the Participant SMO. 8.4.3.4. The Participant SMO logs into the system and views the record for the Participant. The Participant SMO will be able to choose a course of action to take in response to the incident. 8.4.3.5. The Participant SMO suspends access for the Participant. 8.4.3.6. The system shall send a notification to the Hosting SMO. The notification will have a direct link to the Participant's record and allow the Hosting SMO to either allow the Participant to remain on the Visit, remove the Participant from the Visit, or to cancel the Visit. 8.4.4. Business Intelligence 8.4.4.1 Reports will reflect data updates, which occur during the demonstration. • Average Time taken for action taken once incident occurs • Report showing top 10 visit locations 9. RFI Response Format 9.1. Response Requirements: RFI responses must conform to the format below and provide the following information: 9.1.1. Cover Letter. The cover letter must include: 9.1.1.1. Company name, address and CAGECode 9.1.1.2. Company point of contact (telephone number and e-mail address) 9.1.1.3. Date submitted 9.1.1.4. GSA schedule number (if applicable) 9.1.1.5. Company's DUNS 9.1.1.6. Confirm associated business size 9.1.1.7. Company's self-certification under the NAICS 9.1.2. RFI Response 9.1.2.1. The government will assess and analyze responses and may use this information to inform future decisions and potential procurements. The government recognizes that many potential respondents will only have information pertaining to a portion of this RFI. However, partial information may be of high quality and significant value to the development of a new government-wide, end-to-end security clearance process. Therefore, while the government seeks a comprehensive approach, it does not discourage partial responses. 9.1.2.2. The main body of the response should be no more than 10 total single-sided pages with print no smaller than 12 point. The submissions must be in sufficient detail and clarity to provide information needed to assess your approach. Responses must be submitted in Microsoft Word 2003 or later. 9.1.2.3. Vendor should include recent and relevant experience. 9.2. Key considerations 9.2.1. Please factor in the following key considerations where relevant in your responses to the RFI. 9.2.1.1. Technical capabilities: Discuss how your approach is scalable, portable, and interoperable. 9.2.1.2. Tools and Techniques: Discuss the methodologies, processes and products, or services, both existing and emerging included in your approach. 9.2.1.3. Reuse: Where applicable, discuss how your approach leverages existing and emerging capabilities found across the government and elsewhere. 9.2.1.4. Maturity: discuss the maturity of your approach, i.e. distinguish between existing capabilities and those not yet available on the market. 9.2.1.5. Data Security & Privacy: Provide details of how the privacy, security and integrity of the data stored will be ensured 9.2.1.6. Accessibility: Discuss compliance with Section 508 accessibility standards of the Rehabilitation Act (http://www.section508.gov) 9.2.1.7. Certification: Discuss your organization's capability to meet Capability Maturity Model Integration (CMMI) Level 3 assessment. 9.2.1.8. Information Assurance: Discuss how you previously supported the DoD Information Assurance Certification and Accreditation Process (DIACAP) and enabled a favorable certification and accreditation for a system. 9.2.1.9. Data Standardization: Discuss how you plan to standardize the DISS information exchange environment. 10. Response Questionnaire 10.1. General Approach 10.1.1. The DISS Program Management Office is seeking input from qualified vendors to help develop the Joint Verification System and Enterprise Application Integration and Portal Services component for the DISS system. Using the above information as context, describe your overall approach/vision for developing this component to the DISS Department-wide, end-to-end security clearance process. 10.2. Specific Capabilities 10.2.1. Capabilities currently gathered from community input are outlined in Sections 7.2 and 7.3 of the RFI. These capabilities do not represent a comprehensive list but should be considered when replying to the RFI. 10.2.2. Provide an enterprise framework for the full human and system connectivity and interoperability that allows all DISS users and mission partners to share the information they need, when they need it, in a form they can understand and act on with confidence, and to protect information from thosewho should not have it. 10.3. Implementation 10.3.1. Describe the high-level steps involved in planning, preparing, and implementing your approach and include estimated timelines. 10.3.2. Identify and describe instances where your approach was implemented in a similar context or environment. 10.4. Scenarios 10.4.1. Identify specific areas of the scenarios that have high impacts in terms of change management (E.g. are there specific processes demonstrated that impart more change on end users than others) 10.4.2. Vendors should include samples of reports to demonstrate the processes described in the RFI scenarios. 10.5. Risk Management 10.5.1. Discuss in detail how your approach manages risk 10.5.2. Identify any significant concerns, potential pitfalls and/or risks relate dot the implementation of your approach. Include both near and long term considerations. Discuss your approach to tracking and managing the critical risks. 10.6. Cost and Benefit 10.6.1. Discuss the high-level cost estimates and benefits for your proposed approach. Include development and sustainment costs. 10.6.2. Highlight the elements of timeliness, quality and cost, identifying where the tradeoff opportunities exist between each. 11. Instructions to Prospective Respondents 11.1. Responses to the RFI must be submitted to Mike Young, Deputy Program Manager, DISS, by 3:00 PM ET, Tuesday, July 13th, 2010. E-mail one soft copy and mail one hard copy (received prior to closing date/time) of all response files to: DISS - Business Transformation Agency Attn: Mike Young 1851 S. Bell Street Arlington, VA 22202 11.2. Questions regarding any aspect of this acquisition should be e-mailed to Michael.Young@bta.mil. Questions and/or responses concerning the RFI process may be posted as an amendment to the DISS RFI at the government's discretion. 11.3. Late Submissions: Late submissions may or may not be considered. This decision is left to the discretion of the DISS PMO.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/DISA/D4AD/DITCO/BTA2010-01/listing.html)
- Record
- SN02189998-W 20100630/100628235002-841af568a6c2e3cd4fc49ee12bd399cd (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 |