For organisations planning digital systems and information services.
Computer systems,
data processing and
information access.
ILHAMI LIMITED brings together computer systems design, computing infrastructure, data processing, web hosting and information retrieval. These activities address connected questions: how should information be organised, what should happen to it, where should it operate and how will people find what they need?
Start with the task your organisation needs to perform: a new system, an existing dataset, a hosted resource or a clearer route through a collection.
Connected activities
Begin with the problem
in front of you.
A systems project may begin with disconnected tasks. A processing requirement may begin with inconsistent files. An information service may begin with material that exists but is difficult to locate.
Choose the closest starting point. These activities relate to one another, but the scope should follow the requirement.
Computer systems design
Give the system
a clear structure.
Systems design starts with the work a system must support: its users, inputs, processing steps and required outputs. The connections between those parts matter as much as the individual components.
A brief can cover workflow mapping, system boundaries, information structures and relationships between existing and proposed components. Potential deliverables include a requirements outline, a system diagram, interface specifications and acceptance criteria.
This may mean replacing disconnected manual steps, defining an exchange between applications or planning a digital service. The design should be reviewable against the original requirement.
- Inputs
- Who supplies information, in what form, and at which point?
- Processing
- Which rules, decisions and exchanges move the work forward?
- Outputs
- What must the system produce, and how will it be assessed?
Data preparation & processing
Turn source material
into consistent records.
Preparation concerns the condition and structure of information before use. Processing applies the operations needed to produce a useful output. Both depend on clear rules.
item: BR-7
group: Reference
format: pdf
ref BR-8
type / reference
file / PDF
Map field names.
Standardise values.
Flag exceptions.
| Reference | Category | Format |
|---|---|---|
| BR-7 | Reference | |
| BR-8 | Reference |
A brief might identify source formats, required fields, inconsistent values, duplicates or the structure required by a destination system. Possible deliverables include a field map, transformation rules, a prepared dataset and an exception record.
Several differently structured files may need a common format before they can be combined. Agreeing how missing or ambiguous values are handled helps prevent assumptions from becoming hidden errors.
Computing infrastructure & web hosting
Plan where the
service will operate.
The operating environment should follow what must run, how it will be accessed and who will be responsible for it.
Information retrieval & portals
Make the right information
easier to find.
Useful access depends on how material is described, grouped, indexed and presented. A search interface is one part of that relationship.
Illustrative collection index
A brief can consider categories, searchable fields, navigation and result descriptions. Deliverables may include an information structure, metadata specification, indexing outline and example retrieval journeys. Exact-reference searches, subject browsing and narrowing a broad result set each suggest different requirements.
Working towards a defined requirement
From an initial question
to an agreed scope.
Understand
Describe the intended outcome, current situation and available materials. Identify relevant activities, constraints and dependencies.
Outcome & contextDefine
Agree deliverables and how they will be assessed: requirements, transformation rules, an environment specification or an access structure.
Scope & criteriaReview
Establish review points and responsibilities. Compare the work with the agreed brief and resolve questions within that scope.
Evidence & decisionsHandover
Identify the documentation and materials to transfer. Make any further implementation, operation or support explicit.
Materials & ownership
Practical considerations
Questions worth
settling early.
- Can a brief focus on one activity?
- Describe the specific requirement first. Related work can be identified during scoping without assuming every activity is needed.
- Can existing systems or files be the starting point?
- Include their formats, dependencies and known limitations. Suitability for reuse needs assessment in context.
- What determines timing and cost?
- Scope, complexity, available inputs and dependencies need to be understood before a project-specific proposal can be established.
- Is ongoing operation included?
- Hosting, maintenance, support and changes require explicit agreement about responsibilities and coverage.
ILHAMI LIMITED
Connected by the
information they serve.
Our business activities span computer systems design and related computer services, computing infrastructure, data processing and preparation, web hosting, web search portals and information retrieval services.
Together, they concern the organisation, operation and accessibility of digital information. Each engagement needs a defined scope, deliverables and responsibilities.
Start with a useful question
Tell us what
needs to work.
Send a short description of your system, data, hosting or information-access requirement. Include the intended outcome, what already exists and any known constraints or target dates. A concise overview is enough to begin the conversation.