Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY - FEDBIZOPPS ISSUE OF AUGUST 31, 2017 FBO #5760
MODIFICATION

A -- Mission Oriented Information Management (MOIM)

Notice Date
8/29/2017
 
Notice Type
Modification/Amendment
 
NAICS
541712 — Research and Development in the Physical, Engineering, and Life Sciences (except Biotechnology)
 
Contracting Office
Department of the Air Force, Air Force Materiel Command, AFRL/RIK - Rome, 26 Electronic Parkway, Rome, New York, 13441-4514, United States
 
ZIP Code
13441-4514
 
Solicitation Number
BAA-RIK-2014-0011
 
Point of Contact
Gail E. Marsh, Phone: 315-330-7518
 
E-Mail Address
Gail.Marsh@us.af.mil
(Gail.Marsh@us.af.mil)
 
Small Business Set-Aside
N/A
 
Description
AMENDMENT 3 to BAA RIK-2014-0011 The purpose of this modification is to republish the original announcement, incorporating any previous amendments, pursuant to FAR 35.016(c). This republishing also includes the following changes: (a) Section III: Updated to reflect current access requirements; (b) Section IV.3.a: Revised to reflect current NISPOM change; (c) Section IV.4.b & c: Updated date of cited clauses (d) Section VI.1: Updated proposal guidance (e) Section VI.5: Updated to reflect current information; and (f) Section VII: Revised/Updated Ombudsman. No other changes have been made. _________________________________________ NAICS CODE: 541712 FEDERAL AGENCY NAME: Department of the Air Force, Air Force Materiel Command, AFRL - Rome Research Site, AFRL/Information Directorate, 26 Electronic Parkway, Rome, NY, 13441-4514 BROAD AGENCY ANNOUNCEMENT (BAA) TITLE: Mission Oriented Information Management (MOIM) BAA ANNOUNCEMENT TYPE: Initial announcement BAA NUMBER: BAA RIK-2014-0011 CATALOG OF FEDERAL DOMESTIC ASSISTANCE (CFDA) Number: 12.800 I. FUNDING OPPORTUNITY DESCRIPTION: The Information Directorate of the Air Force Research Laboratory (AFRL/RI), Rome Research Site, is soliciting white papers under this announcement for innovative technologies to enable the effective management of information for military operations. AFRL/RI conducts research in the areas of information management and dissemination. Resultant approaches have focused on the creation of services-based information management techniques. This research has led to the development of service oriented information management and dissemination implementations, in particular Phoenix Prime. The continued development and maturation of innovative concepts and enhanced services that maximize the value of information to support the objectives of military operations is the primary focus of this BAA. Background: The Information Management Technologies Branch of the Information Directorate of the Air Force Research Laboratory (AFRL), Rome Research Site, are researching and developing techniques and services for information management in diverse military environments. Information Management (IM) is defined as a set of intentional activities to maximize the value of information to support the objectives of the military enterprise. These activities include role/policy based information access control, information tagging and contextualization through semantic assessment, discovery and identification, scalability and responsiveness to resource availability and the administrative activities that support them. Understanding how concepts for sharing information amongst disparate producers, consumers and operational domains and the technologies that can be applied in the unique military operational and tactical domains are of critical importance. Multi-Domain Interoperability (MDI) continues to emerge across the AF and DoD as a growing and pervasive information sharing requirement. The need exists across command echelons, military services, security domains, coalitions and civilian entities. The MDI problem is more complex, however, than just sharing information by invoking services or querying databases in other domains. From the consumer's perspective it is difficult to know if the information exists, where it exists, how to access it if policy permits and whether or not it is in a usable form. While the information owners must determine to whom access should be granted, what information is releasable under what conditions and how many resources to make available to service extra-domain needs. Addressing these information discovery, access and policy issues is necessary but insufficient to add value to the supported operational processes if it only results in low quality information overloading the systems and users. The solution to information sharing must be more comprehensive to enable the identification and delivery of mission relevant information within mission time-scales. AFRL's information centric technology vision has culminated in a suite of AFRL Information Management (IM) services known as Phoenix Prime. Phoenix Prime is a service oriented information system that enables the management of all information interactions through domain independent "universal services" whose functions include obtaining, discovering, characterizing, identifying, prioritizing, mediating, persisting and disseminating information within and between mission partners. The most recent Phoenix Prime developments correlate users with operational activities, determine information requirements, assess information for mission relevance and establish information processing priorities based upon mission importance and system resource availability. The research and development to be conducted under this BAA are as follows: • Augment and mature the AFRL Phoenix Prime services to produce highly scalable mission oriented middleware that semantically characterizes and contextualizes information for the automatic identification and delivery of mission relevant information to consumers in federated environments. • Demonstrate the capabilities in operationally relevant environments. FY15 FOCUS AREA: Coalesce The goal of project Coalesce is to mature the existing suite of Phoenix Prime IM services and develop new capabilities required for automatic, secure, scalable mission relevant information identification and delivery across federated domains. The key challenges to be addressed in this project are service scalability, federated information identification and delivery, mission information characterization, multi-aspect policy complexity and experimentation. The existing Phoenix Prime federation services will be enhanced to accommodate cross-federate policy controlled information discovery and relevancy assessment. Use cases of viable approaches will be defined and evaluated leading to an implementation that enables the federation services to effectively share information and relevancy requirements in multi-partner environments. During the Coalesce project, the Adaptive Mission Template (AMT) capability developed under the AFRL Mission Responsive Information Services program will be integrated with the Phoenix Prime services and configured with domain specifics to meet experimentation and demonstration goals. The goal of AMT is to define the role-based mission relevant information requirements for each actor in support of active missions via ontological definitions. AMT is a tool set that has both design time and run-time aspects. The design time tools enable templates to be defined which will be activated at run-time and adapted to active mission information with template variables such as area of regard. Coalesce will mature the current semantic characterization services of Phoenix Prime through experimentation with a particular focus on determining mission relevancy and optimizing performance. The standard approach to semantic knowledge base (Resource Description Framework [RDF] triple stores) developments involves extracting triples from bulk datasets to perform off line analytics. The prototype semantic services of Phoenix Prime support this approach but its innovative use case is to extract the relationships from all information at publication time in preparation to broker against semantic subscriptions. The Phoenix Prime semantic augmentations will result from an evaluation of the appropriate technologies and use for semantic reasoning/inferencing with respect to relevancy determination in the federated IM and domain specific contexts. Coalesce will exploit cloud computing and virtualization technologies to provision sufficient computational resources for high demand semantic processing of large information flows to support mission relevant information dissemination within mission timeline constraints during mission run-time. Current Phoenix Prime services can be deployed as a scalable cluster (IM as a service) but its repositories and semantic technologies (semantics as a service) are not currently part of that implementation. In order for these IM services to be transitioned they must be relatively easy to deploy, configure, administer and monitor. To that end, Coalesce will develop a capability that enables administrators to efficiently monitor all aspects of IM system state, define and modify service configurations and define and deconflict all domain specific policies. Ease of deployment will also require the porting of Phoenix Prime services to domain appropriate Service Oriented Architecture stacks. Coalesce will conduct annual experiments/demonstrations that will act as capability checkpoints or "off-ramps" in operationally relevant scenarios and domains. AFRL/RIS has a number of available test beds that will be considered for use. These experimentation environments include UNITY (multi-national, cross domain federation), Synchronized Operations (Interoperable Air, Space and Cyber federation) and various RISA cloud test beds. A particular emphasis will be on the space domain due to growing relationships and opportunities for transition. Offerors are encouraged to provide an onsite (AFRL/RISA, Rome, NY) contractor presence to foster collaboration with other in-house teams, to minimize integration risks and to effectively leverage experimentation/demonstration resources. AFRL/RISA is prepared to provide computer lab work area for up to 6 simultaneous developers. Each of the available work areas will include desk, chair, computer, phone and network and printer access. GOVERNMENT FURNISHED SOFTWARE: Phoenix Prime software and documentation are available upon request to Timothy Blocher ( timothy.blocher@us.af.mil ). Security Classification: Software development will largely be UNCLASSIFIED but the domain specific activities may be up to TS/SCI. II. AWARD INFORMATION: 1. FUNDING: Total funding for this BAA is approximately $9.9M. The anticipated funding to be obligated under this BAA is broken out by fiscal year as follows: FY15 - $2.65M FY16 - $2.65M FY17 - $2.3M FY18 - $2.3M Individual awards will not normally exceed 24 months with dollar amounts normally ranging from $250K to $1.25M. There is also the potential to make awards up to any dollar value. The Government reserves the right to select all, part, or none of the proposals received, subject to the availability of funds. All potential Offerors should be aware that due to unanticipated budget fluctuations, funding in any or all areas may change with little or no notice. 2. FORM. Awards of efforts as a result of this announcement will be in the form of contracts. 3. BAA TYPE: This is a two-step open broad agency announcement. This announcement constitutes the only solicitation. As STEP ONE - We are only soliciting white papers at this time. DO NOT SUBMIT A FORMAL PROPOSAL. Those white papers found to be consistent with the intent of this BAA may be invited to submit a technical and cost proposal, see Section VI of this announcement for further details regarding the proposal. III. ELIGIBILITY INFORMATION: All qualified offerors who meet the requirements of this BAA may apply. Foreign or foreign-owned offerors are advised that their participation is subject to foreign disclosure review procedures. Foreign or foreign-owned offerors should immediately contact the contracting office focal point, Gail E. Marsh, Contracting Officer, telephone (315) 330-7518 or e-mail Gail.Marsh@us.af.mil for information if they contemplate responding. The e-mail must reference the BAA number and title. Contractor employees requiring access to USAF bases, AFRL facilities, and/or access to U.S. Government Information Technology (IT) networks in connection with the work on contractual actions awarded under this BAA must be U.S. citizens. For the purpose of base and network access, possession of a permanent resident card ("Green Card") does not equate to U.S. citizenship. This requirement does not apply to foreign nationals approved by the U.S. Department of Defense or U.S. State Department under international personnel exchange agreements with foreign governments. Any waivers to this requirement must be granted in writing by the Contracting Officer prior to providing access. The above requirements are in addition to any other contract requirements related to obtaining a Common Access Card (CAC). If an IT network/system does not require AFRL to endorse a contractor's application to said network/system in order to gain access, the organization operating the IT network/system is responsible for controlling access to its system. If an IT network/system requires a U.S. Government sponsor to endorse the application in order for access to the IT network/system, AFRL will only endorse the following types of applications, consistent with the requirements above: 1. Contractor employees who are U.S. citizens performing work under contractual actions awarded under this BAA. 2. Contractor employees who are non-U.S. citizens and who have been granted a waiver. Any additional access restrictions established by the IT network/system owner apply. IV. APPLICATION AND SUBMISSION INFORMATION: All responses to this announcement must be addressed to the Technical point of contact (POC) listed in SECTION VII. DO NOT send white papers to the Contracting Officer. 1. SUBMISSION DATES AND TIMES: It is recommended that white papers be received by the following dates to maximize the possibility of award: FY15 by 18 Sep 2014 FY16 by 1 Sep 2015 FY17 by 1 Sep 2016 FY18 by 31 Aug 2017 White papers will be accepted until 2 PM Eastern Time on 28 Sep 2018, but it is less likely that funding will be available in each respective fiscal year after the dates cited. This BAA will close on 28 Sep 2018. All offerors submitting white papers will be contacted by the technical POC, referenced in Section VII of this announcement. Offerors can email the technical POC for status of their white paper/proposal no earlier than 45 days after submission. 2. CONTENT AND FORMAT: Offerors are required to submit 2 copies of a 5-6 page white paper summarizing their proposed approach/solution. The purpose of the white paper is to preclude unwarranted effort on the part of an offeror whose proposed work is not of interest to the Government. The white paper will be formatted as follows: a. Section A : Title, Period of Performance, Estimated Cost, Name/Address of Company, Technical and Contracting Points of Contact (phone, fax and email)(this section is NOT included in the page count); b. Section B : Task Objective; and c. Section C : Technical Summary and Proposed Deliverables. All white papers shall be double spaced with a font no smaller than 12 point. In addition, respondents are requested to provide their Commercial and Government Entity (CAGE) number, their Dun & Bradstreet (D&B) Data Universal Numbering System (DUNS) number, a fax number, an e-mail address, and reference BAA-RIK-2014-0011 with their submission. Multiple white papers within the purview of this announcement may be submitted by each offeror. If the offeror wishes to restrict its white papers, they must be marked with the restrictive language stated in FAR 15.609(a) and (b). 3. HANDLING AND MAILING INSTRUCTIONS: a. CLASSIFICATION GUIDANCE. All Proposers should review the NATIONAL INDUSTRIAL SECURITY PROGRAM OPERATING MANUAL, (NISPOM), dated February 28, 2006 and as amended by Change 2 dated May 18, 2016, as it provides baseline standards for the protection of classified information and prescribes the requirements concerning Contractor Developed Information under paragraph 4-105. Defense Security Service (DSS) Site for the NISPOM is: http://www.dss.mil/. In the event of a possible or actual compromise of classified information in the submission of your white paper or proposal, immediately but no later than 24 hours, bring this to the attention of your cognizant security authority and AFRL Rome Research Site Information Protection Office (IPO): Vincent Guza 315-330-4048 0730-1630 Monday-Friday 315-330-2961 Evenings and Weekends Email: vincent.guza@us.af.mil b. CLASSIFIED SUBMISSIONS. AFRL/RISA will accept classified responses to this BAA when the classification is mandated by classification guidance provided by an Original Classification Authority of the U.S. Government, or when the offeror believes the work, if successful, would merit classification. Security classification guidance in the form of a DD Form 254 (DoD Contract Security Classification Specification) will not be provided at this time since AFRL is soliciting ideas only. Offerors that intend to include classified information or data in their white paper submission or who are unsure about the appropriate classification of their white papers should contact the technical point of contact listed in Section VII for guidance and direction in advance of preparation. c. MAILING INSTRUCTIONS. All mailed responses to this announcement must be sent U.S. Postal Service, registered mail and addressed to AFRL/RISA, 525 Brooks Road, Rome NY 13441-4505, and reference BAA RIK-2014-0011. When mailing follow the directions regarding the number of copies required. Electronic submission to Timothy W. Blocher will also be accepted. Encrypt or password-protect all proprietary information prior to sending. Offerors are responsible to confirm receipt with the technical POC listed in Section VII. AFRL is not responsible of undelivered documents. If electronic submission is used, only one copy of the documentation is required. Questions can be directed to the technical POC listed in Section VII. 4. OTHER SUBMISSION REQUIREMENTS/CONSIDERATIONS: a. COST SHARING OR MATCHING: Cost sharing is not a requirement. b. SYSTEM FOR AWARD MANAGEMENT (SAM). Offerors must be registered in the SAM database to receive a contract award, and remain registered during performance and through final payment of any contract or agreement. Processing time for registration in SAM, which normally takes forty-eight hours, should be taken into consideration when registering. Offerors who are not already registered should consider applying for registration before submitting a proposal. The provision at FAR 52.204-7, System for Award Management (Oct 2016) applies. c. EXECUTIVE COMPENSATION AND FIRST-TIER SUBCONTRACT/ SUBRECIPIENT AWARDS: Any contract award resulting from this announcement may contain the clause at FAR 52.204-10 - Reporting Executive Compensation and First-Tier Subcontract Awards (Oct 2016). d. ALLOWABLE CHARGES: The cost of preparing white papers/proposals in response to this announcement is not considered an allowable direct charge to any resulting contract or any other contract, but may be an allowable expense to the normal bid and proposal indirect cost specified in FAR 31.205-18. e. GOVERNMENT APPROVED ACCOUNTING SYSTEM: An offeror must have an government approved accounting system prior to award of a cost-reimbursement contract per limitations set forth in FAR 16.301-3(a) to ensure the system is adequate for determining costs applicable to the contract. The acceptability of an accounting system is determined based upon an audit performed by the Defense Contract Audit Agency (DCAA). IMPORTANT : If you do not have a DCAA approved accounting system access the following link for instructions: https://www.fbo.gov/index?s=opportunity&mode=form&id=1cffad228f48b58057072a6c9113799d&tab=core&_ cview=1 V. APPLICATION REVIEW INFORMATION: 1. CRITERIA: The following criteria, which are listed in descending order of importance, will be used to determine whether white papers and proposals submitted are consistent with the intent of this BAA and of interest to the Government: a. Overall Scientific and Technical Merit -- Including the approach for the development and/or enhancement of the proposed technology and its evaluation, b. Related Experience - The extent to which the offeror demonstrates relevant technology and domain knowledge, c. Openness/Maturity and Assurance of Solution - The extent to which existing capabilities and standards are leveraged and the relative maturity of the proposed technology in terms of reliability and robustness, and d. Reasonableness and realism of proposed costs and fees (if any). No further evaluation criteria will be used in selecting white papers/proposals. White papers and proposals submitted will be evaluated as they are received. 2. REVIEW AND SELECTION PROCESS: Only Government employees will evaluate the white papers/proposals for selection. The Air Force Research Laboratory's Information Directorate has contracted for various business and staff support services, some of which require contractors to obtain administrative access to proprietary information submitted by other contractors. Administrative access is defined as "handling or having physical control over information for the sole purpose of accomplishing the administrative functions specified in the administrative support contract, which do not require the review, reading, and comprehension of the content of the information on the part of non-technical professionals assigned to accomplish the specified administrative tasks." These contractors have signed general non-disclosure agreements and organizational conflict of interest statements. The required administrative access will be granted to non-technical professionals. Examples of the administrative tasks performed include: a. Assembling and organizing information for R&D case files; b. Accessing library files for use by government personnel; and c. Handling and administration of proposals, contracts, contract funding and queries. Any objection to administrative access must be in writing to the Contracting Officer and shall include a detailed statement of the basis for the objection. 3. ADEQUATE PRICE COMPETITION: The Government may simultaneously evaluate proposals received under this BAA with a common cutoff date for multiple offerors. In this case, the Government may make award based on adequate price competition, and offerors must be aware that there is a possibility of non-selection due to a proposal of similar but higher-priced technical approach as compared to another offeror. 4. FEDERAL AWARDEE PERFORMANCE AND INTEGRITY INFORMATION SYSTEM (FAPIIS) PUBLIC ACCESS: The Government is required to review and consider any information about the applicant that is in the FAPIIS before making any award in excess of the simplified acquisition threshold (currently $150,000) over the period of performance. An applicant may review and comment on any information about itself that a federal awarding agency previously entered. The Government will consider any comments by the applicant, in addition to other information in FAPIIS in making a judgment about the applicant's integrity, business ethics, and record of performance under federal awards when completing the review of risk posed by applicants as described in 2 CFR § 200.205 Federal Awarding Agency Review of Risk Posed by Applicants and per FAR 9.104-6 FAPIIS. VI. STEP TWO INFORMATION - REQUEST FOR PROPOSAL & AWARD: 1. AWARD NOTICES: Those white papers found to be consistent with the intent of this BAA may be invited to submit a technical and cost proposal. Notification by email or letter will be sent by the technical POC. Such invitation does not assure that the submitting organization will be awarded a contract. Those white papers not selected to submit a proposal will be notified in the same manner. Prospective offerors are advised that only Contracting Officers are legally authorized to commit the Government. For additional information when developing proposals, reference the AFRL "Broad Agency Announcement (BAA): Guide for Industry," Mar 2015, and RI-Specific Proposal Preparation Instructions, Jan 2017, which may be accessed at: https://www.fbo.gov/index?s=opportunity&mode=form&id=1cffad228f48b58057072a6c9113799d&tab=core&_ cview=1. Always reference the newest versions of these documents. 2. ADMINISTRATIVE AND NATIONAL POLICY REQUIREMENTS: Depending on the work to be performed, the offeror may require a SECRET or TOP SECRET facility clearance and safeguarding capability; therefore, personnel identified for assignment to a classified effort must be cleared for access to SECRET or TOP SECRET/SCI information at the time of award. In addition, the offeror may be required to have, or have access to, a certified and Government-approved facility to support work under this BAA. This acquisition may involve data that is subject to export control laws and regulations. Only contractors who are registered and certified with the Defense Logistics Information Service (DLIS) at http://www.dlis.dla.mil/jcp/ and have a legitimate business purpose may participate in this solicitation. For questions, contact DLIS on-line at http://www.dlis.dla.mil/jcp or at the DLA Logistics Information Service, 74 Washington Avenue North, Battle Creek, Michigan 49037-3084, and telephone number 1-800-352-3572. You must submit a copy of your approved DD Form 2345, Militarily Critical Technical Data Agreement, with your white paper/proposal. 3. DATA RIGHTS: a. SBIR RIGHTS. The potential for inclusion of Small Business Innovation Research (SBIR) or data rights other than unlimited on awards is recognized. In accordance with (IAW) the Small Business Administration (SBA) SBIR Policy Directive, Section 8(b), SBIR data rights clauses are non-negotiable and must not be the subject of negotiations pertaining to an award, or diminished or removed during award administration. Issuance of an award will not be made conditional based on forfeit of data rights. If the SBIR awardee wishes to transfer its SBIR data rights to the Air Force or to a third party, it must do so in writing under a separate agreement. A decision by the awardee to relinquish, transfer, or modify in any way its SBIR data rights must be made without pressure or coercion by the agency or any other party. b. NON-SBIR RIGHTS. Non-SBIR data rights less than unlimited will be evaluated and negotiated on a case-by-case basis. Government Purpose Rights are anticipated for data developed with DoD-reimbursed Independent Research and Development (IR&D) funding. 4. REPORTING: a. Contract Applicable: Once a proposal has been selected for award, offerors will be given complete instructions on the submission process for the reports. b. FAPIIS Applicable: As required by 2 CFR 200 Appendix XII of the Uniform Guidance and FAR 9.104-6, non-federal entities (NFEs) are required to disclose in FAPIIS any information about criminal, civil, and administrative proceedings, and/or affirm that there is no new information to provide. This applies to NFEs that receive federal awards (currently active grants, cooperative agreements, and procurement contracts) greater than $10,000,000 for any period of time during the period of performance of an award/project. 5. NOTICE: The following provisions* apply: (a) FAR 52.209-11, Representation by Corporations Regarding Delinquent Tax Liability or a Felony Conviction under any Federal Law (b) DFARS 252.239-7017, Notice of Supply Chain Risk (c) DFARS 252.204-7008, Compliance with Safeguarding Covered Defense Information Controls * Please note that the current versions or deviations of the related clauses will be included in any resulting contract. 6. GRANT AWARDS ONLY : For efforts proposed as grant awards, offerors must provide an abstract in their proposal (not to exceed one page) that is publicly releasable and that describes - in terms the public may understand - the project or program supported by the grant. The DoD will publically post the abstract to comply with Section 8123 of the Department of Defense Appropriations Act, 2015 (Pub. L. 113-235). VII. AGENCY CONTACTS: All white paper and proposal submissions and any questions of a technical nature shall be directed to the cognizant technical point of contact as specified below (unless otherwise specified in the technical area): TPOC Name: Timothy W. Blocher Mailing Address: 525 Brooks Road, Rome, NY 13441-4505 Telephone: (315) 330-3941 Email: timothy.blocher@us.af.mil Questions of a contractual/business nature shall be directed to the cognizant contracting officer, as specified below (email requests are preferred): Gail Marsh Telephone (315) 330-7518 Email: gail.marsh@us.af.mil Emails must reference the solicitation (BAA) number and title of the acquisition. In accordance with AFFARS 5301.91, an Ombudsman has been appointed to hear and facilitate the resolution of concerns from offerors, potential offerors, and others for this acquisition announcement. Before consulting with an ombudsman, interested parties must first address their concerns, issues, disagreements, and/or recommendations to the contracting officer for resolution. AFFARS Clause 5352.201-9101 Ombudsman (Jun 2016) will be incorporated into all contracts awarded under this BAA. The AFRL Ombudsman and AFRL Alternate Ombudsman are as follows: Ombudsman: Ms Lisette K. LeDuc, 1864 Fourth St. Wright-Patterson AFB OH 45433-7130 937-904-4407 lisette.leduc@us.af.mil Alternate Ombudsman: Ms Kimberly L. Yoder 1864 Fourth St. Wright-Patterson AFB OH 45433-7130 937-255-4967 kimberly.yoder@us.af.mil All responsible organizations may submit a white paper which shall be considered.
 
Web Link
FBO.gov Permalink
(https://www.fbo.gov/spg/USAF/AFMC/AFRLRRS/BAA-RIK-2014-0011/listing.html)
 
Record
SN04652908-W 20170831/170829234334-f75c3ed32c203a9a06d40d12c1dea062 (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 |
ECGrid: EDI VAN Interconnect ECGridOS: EDI Web Services Interconnect API Government Data Publications CBDDisk Subscribers
 Privacy Policy  Jenny in Wanderland!  © 1994-2024, Loren Data Corp.